Hi Ernst,
there is no superclass since InitialContextFactory is an interface which is
implemented
by ApplicationClientInitialContextFactory directly (so every vendor provides
his
own InitialContextFactoryClass...)
It should work like this: when the class is needed it should be loaded by
the class
loader over the net (this is a basic principle of JNDI: load the "driver"
which is
needed for current application, if not already installed on the client).
To be more specific with my error: I get an error from the
java.net.URLClassLoader which
says he(she...?) can't find the specific class (ClassNotFoundException).
Did I miss some setup somewhere ... ?
Greetings, Stefan
----- Original Message -----
From: "Ernst de Haan" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, February 28, 2001 3:54 PM
Subject: Re: orion.jar needed for JNDI-lookup??
> Hi Stefan,
>
> > we are running a Swing-application accessing via HTTP/RMI
> > to an EJB-server. To do the JNDI-lookup class
"com.evermind.server.ApplicationClientInitialContextFactory"
> > is used as describes in the orion-doc.
>
> Do you *need* to downcast to ApplicationClientInitialContextFactory, or
can
> you perhaps use a superclass (InitialContextFactory) ? If so, then you
only
> need the JNDI libraries.
>
> --
> Ernst
>
