hmm, next problem...
I would greatly appreciate a tip, link, hint or example for an efficient way of
doing the JNDI lookup on the 4.0.4.RC2 and EJB 3.0 RC 6, like the "old" style
of just asking for the name of the interface and looking this up
The problem that I have is, that I don?t wish to har
Ok, I have the binding... seems like I missunderstud something there, sorry. I
placed the annotation in the class representing the remote interface for the
bean, that did not work. I now placed the annotation in the bean and so get the
binding I want in the JNDI Tree.
Thx
Marc
View the origi
This might actually rather fit into the JNDI area, but since I?m not sure, I'll
use this thread to continue my questioning:
The Problem that I am having is concerning the binding into the JNDI Tree via
annotations:
After the new naming schema in 4.0.4.RC2 ( RC6 EJB 3.0), my objects get hung as
"
Thx for the fast help !
I did it like this, since a direct lookup (NatPersLstBean/remote) didnt seem to
work, but this does the job:
| ...
| Object xyz = initCtx.lookup("NatPerLstBean");
| NamingContext myNamingContext = (NamingContext)xyz;
| xyz = myNamingContext.lookup("remote");
|
You do a look up on the remote interface class nameanonymous wrote :
INatPersLst persLstI =
(INatPersLst)initCtx.lookup(de.home.test.interfaces.INatPersLstRemote.cla
| ss.getName()); this was the default jndi binding in previous versions of
the jboss ejb3 implementation. Now your ejb3 is bound
Hi first off, thanks for the link. I checked it out, but...
Unfortunately it doesn?t clarify to me why the behaviour of the JNDI
Binding/Naming changed for my code when deploying in 4.0.3SP1 (where it works)
or 4.0.4.RC2 (where it does not work).
I have, of course, checked all config files I know
Have a look at
http://docs.jboss.org/ejb3/app-server/tutorial/jndibinding/jndi.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938413#3938413
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938413
-
