-
1. Re: help on
s.rzytki Feb 8, 2006 8:43 AM (in response to da.ogre)Hello
I had the same problem. I still looking for an answer... :)
Regards Sebastian -
2. Re: help on
wesslan Feb 8, 2006 8:53 AM (in response to da.ogre)Naming convention in JNDI is:
EAR_FILE_WITHOUT_EAR_SUFFIX/BEAN_NAME/remote
and
EAR_FILE_WITHOUT_EAR_SUFFIX/BEAN_NAME/local
So in your case you cannot look up your bean withHello.class.getName()
because this is the old (4.0.3SP1) style. You sould do something like:HelloBean/remote
I can't really remember how it works when just packaging with ejb3...
Regards Peter -
3. Re: help on
theute Feb 8, 2006 8:53 AM (in response to da.ogre)Try a lookup on "Hello/remote" instead of
"Hello.class.getName()"
http://wiki.jboss.org/wiki/Wiki.jsp?page=FromJBossEJB3.0RC3ToRC4PFD
"The default JNDI name for any @Remote or @Local interfaces is no longer the FQN of the interface. It is now EJBNAME/remote or EJBNAME/local respectively." -
-
5. Re: help on
da.ogre Feb 9, 2006 3:56 AM (in response to da.ogre)Many many thanks, guys!
I haven't read that doc about the changes and bumped my head what am I doing wrong, but haven't thought about that. -
6. Re: help on
doegi Feb 10, 2006 9:31 AM (in response to da.ogre)erm, isn't that a bit counterproductive?
I've got a Remote interface that remote clients use, but actually two different implementations depending on the enviroment.
Now with this change the remote client application needs to know what implementation is deployed onto JBoss, and any abstraction that EJB gave us are gone. Why is that? How do you do lookups now w/o knowing what Bean implements the remote interface?
Another thing: Jobss doesn't deploy to EJBNAME/remote but to EARNAME/EJBBEANNAME/remote, so you also need to know the EAR name.
Thanks