I tried this as well, this doesn't work either...how can this work one day
and not the next? Maybe this is a jndi issue...
Robert
>Does anybody know what could cause a javax.naming.NameNotFoundException:
<my
>bean name> not found? I think my .xml files are fine, and I think this
used
>to work!
We've got the same problem - it seems Orion 1.4.4 can't decide whether to
make EJB home interfaces available at "java:comp/env/ejb-name" or just
"ejb-name". We've replaced all our lookup code with something like this:
Object ref = null;
try{
ref = jndiContext.lookup("java:comp/env/ejb/WhateverEJB");
} catch(NamingException ne) {
System.err.println("Failed to find WhateverEJB attempting again
using non-standard mapping");
ref = jndiContext.lookup("WhateverEJB");
}
WhateverHome home = (WhateverHome)PortableRemoteObject.narrow(ref,
WhateverHome.class);
This at least lets the app function. Sometimes the first lookup works,
sometimes not. If and when we see a pattern that implies sort sort of reason
for this strange behaviour, I'll report it to the list.
P. Pontbriand
Canlink Interactive Technologies Inc.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
