Folks,
I am wondering wheather using J2EE CA for Ldap connectivity to Appserver is a right thing?
As we all know,J2EE Connector Architecture talks about the *plugability* btn appservers & back end EIS like sap/peoplesoft etc....
But how about applying J2EE CA for Ldap connectivity?
Does it make sense?
thanks.
-
J2EE CA & Ldap servers (3 messages)
- Posted by: Uday Subbarayan
- Posted on: March 28 2003 23:53 EST
Threaded Messages (3)
- J2EE CA & Ldap servers by Lasse Koskela on March 30 2003 05:55 EST
- J2EE CA & Ldap servers by Uday Subbarayan on March 30 2003 17:32 EST
- J2EE CA & Ldap servers by Lasse Koskela on March 31 2003 08:28 EST
- J2EE CA & Ldap servers by Uday Subbarayan on March 30 2003 17:32 EST
-
J2EE CA & Ldap servers[ Go to top ]
- Posted by: Lasse Koskela
- Posted on: March 30 2003 05:55 EST
- in response to Uday Subbarayan
Why use a connector when you already have JNDI? -
J2EE CA & Ldap servers[ Go to top ]
- Posted by: Uday Subbarayan
- Posted on: March 30 2003 17:32 EST
- in response to Lasse Koskela
I am planning to use Ldap server as a backend datastore for my tree like structure objects not as JNDI server...In this case,is it worth trying J2EE CA? -
J2EE CA & Ldap servers[ Go to top ]
- Posted by: Lasse Koskela
- Posted on: March 31 2003 08:28 EST
- in response to Uday Subbarayan
In the J2EE stack, JNDI is the primary API for accessing directory services. LDAP is a directory (well, more accurately a protocol for accessing a directory).
JNDI should be flexible enough unless you plan to use some vendor proprietary features of the LDAP server.