Andrea Gazzarini

Hi, I have a Oracle WebLogic (10.3) installation with 1 Admin Server and two managed servers.
Each managed server has an enterprise application with one ejb (3.0)

If from server A (EJB A) I try to lookup the EJB B on server B the following line succeeds:

RemoteInterfaceB service = (RemoteInterfaceB)naminfContext.lookup(...);

but if I try to invoke some method on that reference I get a NoSuchMethodException.

Note that:

- My Remote interface is not extending any super interface;
- The reference contains the requested method (I saw it using getClass().getMethods()) so the problem seems to be in the generated proxy.

I have no other information, the scenario is so simple and we are talking about a stupid lookup.

Anybody did fight with this scenario?

Best Regards,
Andrea

Hi, you can use the request.getRemoteUser() where of course "request" is an instance of HttpServletRequest. As Javadoc says :

"Returns the login of the user making this request, if the user has been authenticated, or null if the user has not been authenticated. Whether the user name is sent with each subsequent request depends on the browser and type of authentication. Same as the value of the CGI variable REMOTE_USER"

Hope it helps

Hi, just a little thing : there's no admin & managed server...simply the first server that is running is targeted as admin server.

Hi, I think that the listen address is mycomputer and not localhost. If you open the wls console you can configure node manager properties. try to replace "localhost" with "mycomputer"

Alternatively you can start node manager on localhost using

> startNodeManager localhost 5555

Hi alds, it seems strange because the node manager listens by default on localhost:5555...
Sorry for the stupid questions but : did you start the node manager? ($WL_HOME/server/bin/startNodeManager(.sh | .cmd)

Hallo Jeff,
I think nothing is wrong on your application unless for example you put in your ear some old libraries of WebLogic (i.e. weblogic.jar) but I don't see any reason to do that....

com/bea/wlw/runtime/core/bean/SLSBContainerBean is an internal class used by WebLogic to manage stateless session bean componen.
As Javadoc says regarding the NoClassDefFoundError :

Thrown if the Java Virtual Machine or a ClassLoader instance tries to load in the definition of a class (as part of a normal method call or as part of creating a new instance using the new expression) and no definition of the class could be found.

The searched-for class definition existed when the currently executing class was compiled, but the definition can no longer be found.

So, at the end, a WebLogic class
weblogic.utils.classloaders.GenericClassLoader.defineClass
is trying to load / define
com.bea.wlw.runtime.core.bean.SLSBContainerBean
and this class definition is not found so I think you can do nothing with that....check the thing I mentioned before (old libraries) and check your WebLogic installation.

Though changing the conf/jndi.properties in the jboss installation is going to work, its not the correct place to do this

I'm not agree...why is it the wrong place? If the naming service is located on 11.22.33.44:1099 JBoss is supposed to run with that naming service and therefore it doesn't make sense to have an implicit "default" value of localhost:1099.

Putting the file on the ear has moreless the same meaning of hard-coding that. If you want to change the address(run for example this application on another machine) you must rebuild the archive.
Simply I think that the information related to the external environment shoudln't be inside your archive (if it is a file or you hard-coded that there's a little difference IMO)

Hi Pinkal, you can find some useful information on the following link :

http://www.jboss.org/community/docs/DOC-12525.

I did once and it should be quite easy...

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming.jnp.interfaces
java.naming.provider.url= 11.22.33.44:1099

Hi, one problem I'm seeing is that you forgot the protocol on the provider url. I don't know if it's working also without that. So, according to JBoss Wiki :

You'll need a jndi.properties on the remote client which looks like this: #jboss JNDI properties java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp\://localhost\:1099 java.naming.factory.url.pkgs=org.jnp.interfaces

Anyway, I'm not understanding why don't you edit the conf/jndi.properties under the jboss installation? It's more flexible of inserting that directly inside the ear...

Regards,

Regards,

Hi Viv,
I suppose that you are already using one of the JAAS login module (probably the database login module) configured on <server_conf>/conf/login-config.xml.

So, for example, I have this one on my configuration file:
application-policy name = "jbossmq"> <authentication> <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required"> <module-option name = "unauthenticatedIdentity">guest</module-option> <module-option name = "dsJndiName">java:/DefaultDS</module-option> <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option> <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option> </login-module> </authentication> </application-policy>

I think that simply you should have a look how it is implemented the DatabaseServerLoginModule. After that you can extends or decorate it (it depends on its implementation).

Regards,

"java.lang.NoSuchMethodError: javax.faces.application.ViewHandler.initView(Ljavax/faces/context/FacesContext..." indicates that something is wrong with the version of the Java Faces that you are using...

Have a look at this :
http://java.sun.com/javaee/5/docs/api/javax/faces/application/ViewHandler.html

and at this :
http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/application/ViewHandler.html

This is the same class but the versions are different : in the first one there's the initView(...) method while the other don't have it...

Check the right version of JSF (right means that you need to check the environment that is hosting your application)

Best regards,

A queue is a point-to-point channel and therefore can have n senders and only one receiver (from a single message point of view) : that means that a message could be consumed by only one receiver.

A topic is a publish-subscriber channel and therefore can have n senders and n receivers. That means tat a single message could be consumed by n receivers.

Regards

As I remember you have three perspectives of the Controller...

1) The graphical view where you can see in a graphical way page,actions and connections;
2) The code view where you can see the controller source code;
3) Another view that I don't remmeber the name (action view?) : here you can add your control simply using drag & drop.

Regards

WebLogic is using its own Web Server?
ASP & JSP are two different technologies...I think there's no one web server which is able to support both of them...
ASP application is supposed to run into Microsoft IIS, while JSP needs basically a servlet engine so you can use it on Tomcat, WebSphere, Weblogic, JBoss, etc...

Anyway, the answer to your second question is no...Weblogic (as JEE container) supports "only" Java Server Pages...

Regards,

WebLogic Workshop 8.1 is a very simple environment to work with...you can start to see how to use it having a look to the example project loaded on startup...otherwise there is a book (I saw it in Amazon) but I don't remember the name...
But as I remember the online documetation is valid too and It provides several examples...isn't it?
I have a tutorial (pdf + source code) on BEA Workshop but it is a .zip of many MB...I don't know how I can give you it...

Regards,