Re: Interop again: Using a second application server as
foreign JNDI

Christian Huber <> writes:

Server-to-server the WL factory is the correct one. EJB interop
requires that the local app server be able to interpret remote access
to foreign JNDI providers. Trying to put the remote provider in your
app server classpath is doomed to failure.

andy

> Hi again,
>
> i got another question concerning interoperability in combination with a
foreign JNDI provider. I was trying to define a glassfish server as a foreign
JNDI provider in the BEA console and then define a link for that provider so
that i could do a local lookup that gets forwarded to the glassfish server. 
>
> So far i was not able to get a successful lookup (hence this post, who
knew.. ;-)) At first i tried to use the glassfish context factory in the JNDI
provider, but after adding the needed jar files to the classpath (appsrv-rt.jar,
appsr-adminv.jar) the lookup fails with a NoSuchMethodError, which is the result
of a conflict between the glassfish and the weblogic classes (the two jar files
are the main appserver jars and therefore carry a lot of classes which is very
likely to produce side effects). 
>
> So i tried to use the weblogic context factory instead. This time i got a
little further, but the JNDI name i was trying to lookup could not be found even
though the ejb i wanted to lookup up was deployed properly. With both setups i
used a corbaname-url to specifiy the provider. 
>
> During my attempts to debug this i also queried the glasfish JNDI naming
provider from a stand alone client. When using the glassfish context factory i
can see the ejb being deployed and having the expected name. But when i use the
weblogic context factory i do not see the naming reference to the ejb but only
an internal stub which shows that the ejb is deployed but obviously i cannot
access this one. 
>
> My question here is, what context factory would be correct to use in such a
case? In my opinion it should be the glassfish factory, but obviously i cannot
add those classes to the weblogic's classpath. Is there another mechanism i
could try, or does it simply mean that the glassfish people would have to
provide a stripped down version of their jars to be included in refering
application servers?
>
> Thanks, Chris
>
> --