| <?xml version="1.0" encoding="UTF-8"?> |
| <document> |
| <properties> |
| <author email="akarasulu@apache.org">Alex Karasulu</author> |
| <title>Apache Directory Project: Subprojects</title> |
| </properties> |
| |
| <body> |
| <section name="JNDI"> |
| <p> |
| The Directory Project consists of a number of sub-projects. |
| </p> |
| |
| <table> |
| <tr> |
| <th>Name</th> |
| <th>Description</th> |
| </tr> |
| |
| <tr> |
| <td> |
| <a href="directory-naming/index.html">Naming</a> |
| </td> |
| <td> |
| <p> |
| There is a set of core functionality common to all JNDI providers |
| and JNDI does not necessarily revolve around LDAP and X.500 |
| directories. The naming subproject will contain common JNDI code |
| along with various JNDI provider's. A J2EE ENC, environment |
| naming context would be one implementation. If you're looking to |
| build a JNDI provider you might want to take a look in here before |
| proceeding. |
| </p> |
| </td> |
| </tr> |
| |
| <tr> |
| <td> |
| <a href="apacheds/projects/apacheds-core/index.html">ApacheDS Core</a> |
| </td> |
| <td> |
| <p> |
| ApacheDS' core is also a JNDI provider for the LDAP namespace. |
| This provider is not an LDAP client but operates on entries stored |
| locally on disk within ApacheDS' databases. It is a server-side |
| JNDI LDAP provider in this respect although the concept of a |
| server side JNDI provider is strange. |
| </p> |
| </td> |
| </tr> |
| |
| </table> |
| </section> |
| </body> |
| </document> |
