|
| Re: Interop with WLS 10 and other application servers |
 |
Thu, 3 Jan 2008 02:49:59 -0800 |
Hi,
i think i got a bit closer to solve the problem stated above. When i list all
the contents of the JNDI context provided by the EJB host i do get an entry for
the NamedSecurityBean which i want to look up. But the entry is of the class
weblogic.jndi.internal.ServerNamingNode instead of javax.naming.reference. My
assumption is, that this is the reason i cannot access the EJB from another
application server instance. Can anyone verify this assumption? And if that
really _is_ the cause, then how can i solve this? I deployed the EJB as usual
and the same jar file deployed on a glassfish instance does result in the JNDI
name being available as a javax.naming.reference. Or could this simply be an
internal difference between those two application servers and should not affect
the accessibility at all?
|
| Post Reply
|
|
|
|
|
|
|
|
|
|