I was under impression that all the bindings in the JNDI tree should be
navigable from the root.  So for example, if you bind to ormi://localhost
you should be able to navigate (by looking up or resolving) contexts down to
the application level objects.  As far as the client is concerned, this does
not appear to be the case.

When I configure jndi.properties with ormi://localhost, I see:

jdbc - the context where all the jdbc connections are setup
java:comp - a context which contains ServerAdiministrator, Administrator,
and ResourceFinder

When I configure jndi.properties with ormi://localhost/citysearch, I see the
application related things...

I still have not figured out how to navigate from ormi://localhost over to
ormi://localhost/citysearch.  There is some magic which is occurring between
ormi://localhost and ormi://localhost/citysearch which I am not sure of at
the moment.

-AP_

-----Original Message-----
From: Andre Vanha [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 28, 2000 12:27 PM
To: Alex Paransky
Subject: RE: JNDI naming confusion...


Alex,
I had the same problem and submitted it as a bug to the orion team.
However I'm not sure when it will be fixed.

Andre

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky
Sent: Monday, March 27, 2000 6:45 PM
To: Orion-Interest
Subject: JNDI naming confusion...


When my jndi.properties contains:
java.naming.provider.url=ormi://localhost, I can bind to "jdbc/DefaultDS",
but not any of my application objects
When my jndi.properties contains:
java.naming.provider.url=ormi://localhost/citysearch, I can bind to
application objects, but not to jdbc/DefaultDS.

I am creating BMP objects, and I need access to the jdbc namespace to access
the database, but it seems like I can have one or the other but not both.
Am I doing something wrong?

My jndi.properties looks like this:

java.naming.factory.initial=com.evermind.server.ApplicationClientInitialCont
extFactory
java.naming.provider.url=ormi://localhost/citysearch
java.naming.security.principal=admin
java.naming.security.credentials=123

Also should I be using:

java.naming.factory.initial=com.evermind.server.ApplicationClientInitialCont
extFactory

or

java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

???

Thanks.
-AP_

Reply via email to