not sure about ejb3, but shouldn't this be more like
"java:comp/env/Authenticator" ?
in ejb2 this would be the proper prefix...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027074#4027074
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=
I think the problem I am having is relating to the way I packaged my ear file.
When I unpacked the ear and deployed only the jar file, I had no problem
looking up the remote interfaces.
I would greatly appreciate if someone can help clarifying what I need in my ear
file. O'Reilly's Enterprise J
Have you give JNDI name to your EJB ?
During the déployment, you should see something like this :
[EjbModule] Deploying XXX
| [ProxyFactory] Bound EJB Home 'XXX' to jndi 'X_X'
| [EJBDeployer] Deployed:
file:/C:/jboss-portal-2.4.1/server/default/deploy/XXX.jar
NO ?
View the original post :
No.
I thought with EJB3, the JNDI name should be defaulted the unqualified
classname.
Do I need an explicit JNDI name if I were to deploy with EAR file? Deployment
with JAR did not seem to require the JNDI names at all.
View the original post :
http://www.jboss.com/index.html?module=bb&op=vi
Hi the correct Lookup when deploying in an ear file must be:
Object authenRef =
_intialCtx.lookup("/AuthenticatorBean/remote");
in your case:
Object authenRef = _intialCtx.lookup("test/AuthenticatorBean/remote");
I had the same problem like you before ;-))
Greedings McGerman
View the origina