directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pste...@apache.org
Subject svn commit: r123518 - /incubator/directory/naming/trunk/xdocs/index.xml
Date Tue, 28 Dec 2004 15:53:14 GMT
Author: psteitz
Date: Tue Dec 28 07:53:11 2004
New Revision: 123518

URL: http://svn.apache.org/viewcvs?view=rev&rev=123518
Log:
Updated to reflect new subproject structure. Improved overview.
Modified:
   incubator/directory/naming/trunk/xdocs/index.xml

Modified: incubator/directory/naming/trunk/xdocs/index.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/naming/trunk/xdocs/index.xml?view=diff&rev=123518&p1=incubator/directory/naming/trunk/xdocs/index.xml&r1=123517&p2=incubator/directory/naming/trunk/xdocs/index.xml&r2=123518
==============================================================================
--- incubator/directory/naming/trunk/xdocs/index.xml	(original)
+++ incubator/directory/naming/trunk/xdocs/index.xml	Tue Dec 28 07:53:11 2004
@@ -6,14 +6,59 @@
 
  <body>
 
- <section name="What is Naming?">
+ <section name="Overview">
    <p>
      Naming is a lightweight, in-memory JNDI service provider.  The 
-     initial code base was extracted from the Jakarta Tomcat JNDI implementation.
+     initial code base was extracted from the Jakarta Tomcat JNDI implementation. 
+   </p>
+   <p>
+     The Tomcat implementation is designed to support the "java:comp/env"
+     environment naming context for J2EE web applications. Support for
+     JNDI resource factories and directory and war contexts are included.  
+     In addition, naming contexts can be bound to threads or classloaders
+     and access to contexts can be controlled using security tokens.
+   </p>
+   <p>
+     To provide similar behavior to Tomcat's xml-based configuration of JNDI 
+     resources, an <code>XmlConfigurator</code> is included with Naming.
    </p>
-    
  </section>
- 
+ <section name="Subprojects">
+   <p>
+     To enable flexible deployment with limited dependencies, Naming is
+     divided in 6 subprojects, each producing a separate jar artifact.
+     <table>
+        <tr><th>Subproject</th><th>Description</th><th>Dependencies</th></tr>
+        <tr><td>Naming Core</td>
+            <td>Core JNDI context implementation</td>
+            <td>none</td>
+        </tr>
+        <tr><td>Naming Java</td>
+            <td><code>javaURLContextFactory</code> implementation</td>
+            <td>naming-core</td>
+        </tr>
+        <tr><td>Naming Factory</td>
+            <td>JNDI Object factories</td>
+            <td>naming-core, geronimo-spec-javamail (1.3.1-rc1)</td>
+        </tr>
+        <tr><td>Naming Resources</td>
+            <td>File / web resource contexts</td>
+            <td>naming-core, commons-collections (3.1)</td></tr>
+        <tr><td>Naming Management</td>
+            <td>JMX management interface</td>
+            <td>naming-core, naming-java, mx4j-jmx (1.1.1)</td></tr>
+        <tr><td>Naming Config</td>
+            <td>XML configuration</td>
+            <td>naming-core, naming-factory, naming-java, 
+                commons-logging (1.0.3), commons-collections (3.1),
+                commons-beanutils (1.6.1), commons-digester (1.4.1),
+                commons-lang (1.0.1), commons-dbcp (1.0),
+                commons-pool (1.0.1),
+                hsqldb (1.7.1, test runtime only) 
+            </td></tr>
+      </table>
+    </p>
+   </section>
  </body>
 </document>
 

Mime
View raw message