directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From akaras...@apache.org
Subject svn commit: r124589 - in incubator/directory/server/trunk: core/xdocs main/xdocs plugin/xdocs protocol/xdocs shared/xdocs xdocs xdocs/developers xdocs/projects xdocs/users
Date Fri, 07 Jan 2005 23:24:59 GMT
Author: akarasulu
Date: Fri Jan  7 15:24:55 2005
New Revision: 124589

URL: http://svn.apache.org/viewcvs?view=rev&rev=124589
Log:
Massaged sitedocs where there were references to Eve
Modified:
   incubator/directory/server/trunk/core/xdocs/navigation.xml
   incubator/directory/server/trunk/main/xdocs/navigation.xml
   incubator/directory/server/trunk/plugin/xdocs/navigation.xml
   incubator/directory/server/trunk/protocol/xdocs/navigation.xml
   incubator/directory/server/trunk/shared/xdocs/navigation.xml
   incubator/directory/server/trunk/xdocs/developers/architecture.xml
   incubator/directory/server/trunk/xdocs/developers/backend.xml
   incubator/directory/server/trunk/xdocs/developers/components.xml
   incubator/directory/server/trunk/xdocs/developers/index.xml
   incubator/directory/server/trunk/xdocs/developers/partitions.xml
   incubator/directory/server/trunk/xdocs/developers/protocol.xml
   incubator/directory/server/trunk/xdocs/features.xml
   incubator/directory/server/trunk/xdocs/index.xml
   incubator/directory/server/trunk/xdocs/mailing-lists.xml
   incubator/directory/server/trunk/xdocs/navigation.xml
   incubator/directory/server/trunk/xdocs/projects/index.xml
   incubator/directory/server/trunk/xdocs/roadmap.xml
   incubator/directory/server/trunk/xdocs/users/authentication.xml
   incubator/directory/server/trunk/xdocs/users/building.xml
   incubator/directory/server/trunk/xdocs/users/deploying.xml
   incubator/directory/server/trunk/xdocs/users/index.xml
   incubator/directory/server/trunk/xdocs/users/jndi.xml
   incubator/directory/server/trunk/xdocs/users/partitions.xml
   incubator/directory/server/trunk/xdocs/users/plugin.xml

Modified: incubator/directory/server/trunk/core/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/core/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/core/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/core/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/core/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/core/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -16,25 +16,25 @@
       <item name="SEDA" href="../../../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="../../index.html"/>
       <item name="Features" href="../../features.html"/>
       <item name="Roadmap" href="../../roadmap.html"/>
       <item name="User's Guide" href="../../users/index.html"/>
       <item name="Developer's Guide" href="../../developers/index.html"/>
-      <item name="Eve Projects" href="../../projects/index.html">
-        <item name="main" href="../../projects/eve/index.html"/>
+      <item name="Server Projects" href="../../projects/index.html">
+        <item name="main" href="../../projects/server-main/index.html"/>
         <item name="core" href="/index.html"/>
-        <item name="shared" href="../../projects/eve-shared/index.html"/>
-        <item name="protocol" href="../../projects/eve-protocol/index.html"/>
-        <item name="plugin" href="../../projects/maven-eve-plugin/index.html"/>
+        <item name="shared" href="../../projects/server-shared/index.html"/>
+        <item name="protocol" href="../../projects/server-protocol/index.html"/>
+        <item name="plugin" href="../../projects/maven-directory-plugin/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="../../mailing-lists.html"/>
       <item name="License" href="../../license.html"/>
       <item name="Notices" href="../../notices.html"/>

Modified: incubator/directory/server/trunk/main/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/main/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/main/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/main/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/main/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/main/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -16,25 +16,25 @@
       <item name="SEDA" href="../../../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="../../index.html"/>
       <item name="Features" href="../../features.html"/>
       <item name="Roadmap" href="../../roadmap.html"/>
       <item name="User's Guide" href="../../users/index.html"/>
       <item name="Developer's Guide" href="../../developers/index.html"/>
-      <item name="Eve Projects" href="../../projects/index.html">
+      <item name="Server Projects" href="../../projects/index.html">
         <item name="main" href="/index.html"/>
-        <item name="core" href="../../projects/eve-core/index.html"/>
-        <item name="shared" href="../../projects/eve-shared/index.html"/>
-        <item name="protocol" href="../../projects/eve-protocol/index.html"/>
-        <item name="plugin" href="../../projects/maven-eve-plugin/index.html"/>
+        <item name="core" href="../../projects/server-core/index.html"/>
+        <item name="shared" href="../../projects/server-shared/index.html"/>
+        <item name="protocol" href="../../projects/server-protocol/index.html"/>
+        <item name="plugin" href="../../projects/maven-directory-plugin/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="../../mailing-lists.html"/>
       <item name="License" href="../../license.html"/>
       <item name="Notices" href="../../notices.html"/>

Modified: incubator/directory/server/trunk/plugin/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/plugin/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/plugin/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/plugin/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/plugin/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/plugin/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -16,25 +16,25 @@
       <item name="SEDA" href="../../../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="../../index.html"/>
       <item name="Features" href="../../features.html"/>
       <item name="Roadmap" href="../../roadmap.html"/>
       <item name="User's Guide" href="../../users/index.html"/>
       <item name="Developer's Guide" href="../../developers/index.html"/>
-      <item name="Eve Projects" href="../../projects/index.html">
-        <item name="main" href="../../projects/eve/index.html"/>
-        <item name="core" href="../../projects/eve-core/index.html"/>
-        <item name="shared" href="../../projects/eve-shared/index.html"/>
-        <item name="protocol" href="../../projects/eve-protocol/index.html"/>
+      <item name="Server Projects" href="../../projects/index.html">
+        <item name="main" href="../../projects/server-main/index.html"/>
+        <item name="core" href="../../projects/server-core/index.html"/>
+        <item name="shared" href="../../projects/server-shared/index.html"/>
+        <item name="protocol" href="../../projects/server-protocol/index.html"/>
         <item name="plugin" href="/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="../../mailing-lists.html"/>
       <item name="License" href="../../license.html"/>
       <item name="Notices" href="../../notices.html"/>

Modified: incubator/directory/server/trunk/protocol/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/protocol/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/protocol/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/protocol/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/protocol/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/protocol/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -16,25 +16,25 @@
       <item name="SEDA" href="../../../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="../../index.html"/>
       <item name="Features" href="../../features.html"/>
       <item name="Roadmap" href="../../roadmap.html"/>
       <item name="User's Guide" href="../../users/index.html"/>
       <item name="Developer's Guide" href="../../developers/index.html"/>
-      <item name="Eve Projects" href="../../projects/index.html">
-        <item name="main" href="../../projects/eve/index.html"/>
-        <item name="core" href="../../projects/eve-core/index.html"/>
-        <item name="shared" href="../../projects/eve-shared/index.html"/>
+      <item name="Server Projects" href="../../projects/index.html">
+        <item name="main" href="../../projects/server-main/index.html"/>
+        <item name="core" href="../../projects/server-core/index.html"/>
+        <item name="shared" href="../../projects/server-shared/index.html"/>
         <item name="protocol" href="/index.html"/>
-        <item name="plugin" href="../../projects/maven-eve-plugin/index.html"/>
+        <item name="plugin" href="../../projects/maven-directory-plugin/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="../../mailing-lists.html"/>
       <item name="License" href="../../license.html"/>
       <item name="Notices" href="../../notices.html"/>

Modified: incubator/directory/server/trunk/shared/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/shared/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/shared/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/shared/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/shared/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/shared/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -16,25 +16,25 @@
       <item name="SEDA" href="../../../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="../../index.html"/>
       <item name="Features" href="../../features.html"/>
       <item name="Roadmap" href="../../roadmap.html"/>
       <item name="User's Guide" href="../../users/index.html"/>
       <item name="Developer's Guide" href="../../developers/index.html"/>
-      <item name="Eve Projects" href="../../projects/index.html">
-        <item name="main" href="../../projects/eve/index.html"/>
-        <item name="core" href="../../projects/eve-core/index.html"/>
+      <item name="Server Projects" href="../../projects/index.html">
+        <item name="main" href="../../projects/server-main/index.html"/>
+        <item name="core" href="../../projects/server-core/index.html"/>
         <item name="shared" href="/index.html"/>
-        <item name="protocol" href="../../projects/eve-protocol/index.html"/>
-        <item name="plugin" href="../../projects/maven-eve-plugin/index.html"/>
+        <item name="protocol" href="../../projects/server-protocol/index.html"/>
+        <item name="plugin" href="../../projects/maven-directory-plugin/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="../../mailing-lists.html"/>
       <item name="License" href="../../license.html"/>
       <item name="Notices" href="../../notices.html"/>

Modified: incubator/directory/server/trunk/xdocs/developers/architecture.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/architecture.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/architecture.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/architecture.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/architecture.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/architecture.xml	Fri Jan  7 15:24:55 2005
@@ -11,14 +11,14 @@
         <img src="../images/architecture.png"/>
 
         <p>
-          Eve is actually composed of two separable subsystems: the LDAP protocol
-          provider within the SEDA framework and the Eve JNDI provider (a.k.a.
-          the backend subsystem).
+          The server is actually composed of two separable subsystems: the LDAP
+          protocol provider within the SEDA framework and the JNDI provider
+          (a.k.a. the backend subsystem).
         </p>
 
         <p>
           Below we touch breifly on each major subsystem however a more detailed
-          presentation is available describing Eve's architecture.  It was an
+          presentation is available describing the server's architecture.  It was an
           ApacheCon presentation in 04 and is available
 <a href="https://karasulu.homeip.net/svn/akarasulu/apachecon/eve-presentation/eve-intro-long.ppt">here</a>.
         </p>
@@ -45,7 +45,7 @@
           The LDAP protocol provider contains request handlers for each LDAP
           request PDU type.  These handlers translate LDAP requests into
           operations against an LDAP JNDI provider.  This LDAP JNDI provider by
-          default is the Eve JNDI provider.  However the JNDI provider can be
+          default is the JNDI provider.  However the JNDI provider can be
           switched using environment properties to use the SUN LDAP JNDI
           provider.  When using the SUN JNDI Provider the SEDA protocol provider
           becomes an LDAP proxy server.
@@ -59,43 +59,45 @@
         </p>
       </subsection>
 
-      <subsection name="Eve JNDI Provider">
+      <subsection name="JNDI Provider">
         <p>
           The heart of the server resides within the backend subsystem or the
-          Eve JNDI provider.  The Eve JNDI provider is a JNDI provider for the
+          JNDI provider.  The JNDI provider is a JNDI provider for the
           LDAP namespace.  However this provider does not talk LDAP on the wire,
-          it effects the internal backing stores of Eve directly.  One can think
-          of the Eve JNDI Provider as the server side JNDI provider.
+          it effects the internal backing stores of the server directly.  Hence
+          the JNDI Provider is really the server side JNDI provider.
         </p>
 
         <p>
           Fundamentally JNDI is used as the facade to the entire backend
-          subsystem.  JNDI interfaces are used to operated upon Eve backing
+          subsystem.  JNDI interfaces are used to operated upon server backing
           stores this way.  JNDI also serves as the integration API for
-          embedding Eve.  The EveContextFactory starts up the backend subsystem
-          as well as the networking code when the first initial context is
-          requested.  All other contexts do not incur startup costs.  This
-          unique use of JNDI enables code to simply switch JNDI providers to
-          embed Eve.  It also makes data access code in stored procedures that
-          uses JNDI capable of running inside and outside of the server which
-          makes testing really easy.
+          embedding the server.  The ServerContextFactory starts up the backend
+          subsystem as well as the networking code when the first initial
+          context is requested.  All other contexts do not incur startup costs.
+          This unique use of JNDI enables code to simply switch JNDI providers
+          to embed the server.  It also makes data access code in stored
+          procedures that uses JNDI capable of running inside and outside of
+          the server which makes testing really easy.
         </p>
 
         <p>
-          Eve's backend subsystem contains most of the guts of the server.  We
-          want functionality like replication or triggers to be present
-          regardless of whether Eve is in standalone mode or embedded within
-          another application.  Hence keeping it within the backend made sense.
+          The directory server's backend subsystem contains most of the guts of
+          the server.  We want functionality like replication or triggers to be
+          present there regardless of whether the server is in standalone mode
+          or embedded within another application.  Hence keeping it within the
+          backend made sense.
         </p>
 
         <p>
-          Eve contains backing stores to store LDAP entries which really are
-          serialized javax.naming.directory.Attributes objects.  These entries
-          live within database partitions attached to a naming context.  All
-          entries within these contexts are contained within the partition
+          The server contains backing stores to store LDAP entries which really
+          are serialized javax.naming.directory.Attributes objects.  These
+          entries live within database partitions attached to a naming context.
+          All entries within these contexts are contained within the partition
           assigned to it.  Several partitions can be present within the same
-          Eve instance.  Operations against contexts are routed by a Nexus
-          based on the name (DN) of the entry associated with the operation.
+          directory server instance.  Operations against contexts are routed by
+          a Nexus based on the name (DN) of the entry associated with the
+          operation.
         </p>
 
         <p>

Modified: incubator/directory/server/trunk/xdocs/developers/backend.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/backend.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/backend.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/backend.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/backend.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/backend.xml	Fri Jan  7 15:24:55 2005
@@ -8,7 +8,7 @@
   <body>
     <section name="Backend Subsystem">
       <p>
-        The backend subsystem is everything minux the networking layer and the
+        The backend subsystem is everything minus the networking layer and the
         protocol handling layer.  It is composed of several parts in itself: the
         JNDI provider, interceptor framework, schema subsystem, and database
         subsystem.  Each sub-subsystem of the backend is described in the

Modified: incubator/directory/server/trunk/xdocs/developers/components.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/components.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/components.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/components.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/components.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/components.xml	Fri Jan  7 15:24:55 2005
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Components</title>
+    <title>Server Components</title>
   </properties>
   
   <body>
@@ -43,15 +43,15 @@
         bells and whistles.  However it can run in any micro kernel using
         service wrappers.  A micro kernel is a peice of code operating as a
         component container providing services for that component and running
-        the component through a set of life-cycles.  Eve is designed to run on
-        any micro kernel using component wrappers.  Her subsystems and
+        the component through a set of life-cycles.  The server is designed to run
+        on any micro kernel using component wrappers.  The subsystems and
         components are designed as Plain Old Java Interfaces and Objects (POJIs
         and POJOs) that can be wrapped to make them interoperate within
         different containers.
       </p>
       
       <p>
-        Each component within Eve has a public service interface which 
+        Each component within the server has a public service interface which
         declares what that component can do for its clients.  It is always good
         to keep the interfaces separate from any specific implementations.  You
         can have many implementations for the same service interface.  Secondly
@@ -67,13 +67,14 @@
     <section name="Container Independence">
       <p>
         One of the biggest impediments we've had to deal with while developing
-        Eve and its precursors was having containers go in and out of fashion.
-        We lost several months of development time while switching from Pheonix
-        to Merlin.
+        the server and its precursors was having containers go in and out of
+        fashion.  We lost several months of development time while switching
+        from Pheonix to Merlin for example.  Today we use some custom glue
+        instead.
       </p>
       
       <p>
-        The server has being designed this time from the ground up to be
+        The server has been designed this time from the ground up to be
         independent of any container.  We are doing this by making the default
         implementation of a service a Plain Old Java Object (POJO).  Wrapper
         implementation projects, one for each supported container, are used to
@@ -87,11 +88,11 @@
         container specific code, configuration and build aspects, developers
         no longer need to be aware of container details.  They can focus on the
         core implemenation as a simple class implementing an interface.  Those
-        interested in making Eve run in one container as opposed to another can
-        focus on their container wrapper without the clutter of another 
-        container getting in the way.  This reduces the complexity and learning
-        curve for all those involved in developing Eve's components and 
-        subsystems.
+        interested in making the server run in one container as opposed to
+        another can focus on their container wrapper without the clutter of
+        another container getting in the way.  This reduces the complexity and
+        learning curve for all those involved in developing the directory
+        server's components and subsystems.
       </p>
     </section>
     

Modified: incubator/directory/server/trunk/xdocs/developers/index.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/index.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/index.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/index.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/index.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/index.xml	Fri Jan  7 15:24:55 2005
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Developer's Guide</title>
+    <title>Developer's Guide</title>
   </properties>
   
   <body>
@@ -21,7 +21,7 @@
             <a href="./architecture.html">Architecture</a>
           </td>
           <td>
-            Eve's high level architecture.
+            The server's high level architecture.
           </td>
         </tr>
 
@@ -30,7 +30,7 @@
             <a href="./components.html">Components</a>
           </td>
           <td>
-            How we do components in Eve.
+            How we do components in the directory server.
           </td>
         </tr>
 
@@ -39,7 +39,7 @@
             <a href="./networking.html">Networking</a>
           </td>
           <td>
-            Describes Eve's networking layer.
+            Describes the directory servers's networking code.
           </td>
         </tr>
 

Modified: incubator/directory/server/trunk/xdocs/developers/partitions.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/partitions.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/partitions.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/partitions.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/partitions.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/partitions.xml	Fri Jan  7 15:24:55 2005
@@ -14,7 +14,7 @@
 
       <ul>
         <li><a href="./xldbm.pdf">Paper LDAP database design by Tim Howes</a></li>
-        <li><a href="./alias-dereferencing.pdf">Paper on Eve alias dereferencing mechanism by Alex Karasulu</a></li>
+        <li><a href="./alias-dereferencing.pdf">Paper on alias dereferencing mechanism by Alex Karasulu</a></li>
       </ul>
     </section>
   </body>

Modified: incubator/directory/server/trunk/xdocs/developers/protocol.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/developers/protocol.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/developers/protocol.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/developers/protocol.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/developers/protocol.xml	(original)
+++ incubator/directory/server/trunk/xdocs/developers/protocol.xml	Fri Jan  7 15:24:55 2005
@@ -6,7 +6,7 @@
   </properties>
   
   <body>
-    <section name="Eve's LDAP Protocol Provider">
+    <section name="Server's LDAP Protocol Provider">
       <subsection name="Provider API">
         <p>
           The network layer regardless of the implementation used (seda, sedang,
@@ -18,27 +18,27 @@
         </p>
 
         <p>
-          Like other protocols Eve has a protocol provider implementation.  This
-          implementation is for the LDAP protocol.  The provider is rather simple
-          in nature and has some unique properties which make it flexible enough
-          to be used as an LDAP proxy server or an X.500 gateway server.
+          The directory server has one or more protocol provider
+          implementations.  The primary implementation is for the LDAP protocol.
+          The provider is rather simple in nature and has some unique properties
+          which make it flexible enough to be used as an LDAP proxy server or
+          an X.500 gateway server.
         </p>
       </subsection>
 
       <subsection name="Design">
         <p>
-          Eve's LDAP protocol provider translates on the wire LDAP requests into
-          JNDI LDAP operations.  Results from JNDI operations are then
-          translated to LDAP responses pushed out on the wire.  This thin
-          implementation makes the Eve protocol layer efficient and easy to
-          grasp.
+          The server's LDAP protocol provider translates on the wire LDAP
+          requests into JNDI LDAP operations.  Results from JNDI operations are
+          then translated to LDAP responses pushed out on the wire.  This thin
+          implementation makes the protocol layer efficient and easy to grasp.
         </p>
 
         <p>
           The protocol provider is independent of the JNDI provider used.  It is
           however dependent on the LDAP namespace.  Hence it can only work with
-          LDAP JNDI providers like the SUN LDAP JNDI provider and Eve's JNDI
-          provider.
+          LDAP JNDI providers like the SUN LDAP JNDI provider and the server's
+          JNDI provider.
         </p>
 
         <p>

Modified: incubator/directory/server/trunk/xdocs/features.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/features.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/features.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/features.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/features.xml	(original)
+++ incubator/directory/server/trunk/xdocs/features.xml	Fri Jan  7 15:24:55 2005
@@ -2,13 +2,13 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Eve's Features</title>
+    <title>Apache Directory Project: Server's Features</title>
   </properties>
   
   <body>
-    <section name="Eve's Features">
+    <section name="Server's Features">
       <p> 
-        The Eve Directory Server is an embeddable LDAP server implemented in 
+        The Apache Directory Server is an embeddable LDAP server implemented in
         pure Java.  It has several features that make it unique amoung LDAP 
         servers.  These features are described below:
       </p>
@@ -17,26 +17,26 @@
         <li>
           Designed as an LDAP and X.500 experimentation platform.  Plugable
           components and subsystems make Eve extremely modular and perfect for
-          experiments with various aspects of the LDAP protocol.  Eve be made to
-          can run on any IoC based microkernel using IoC type wrappers for her
-          POJO components implementing POJI services.
+          experiments with various aspects of the LDAP protocol.  The server
+          may be made to can run on any IoC based microkernel using IoC type
+          wrappers for POJO components implementing POJI services.
         </li>
         
         <li>
-          Eve's frontend is completely separable from its backend and 
+          The server's frontend is completely separable from its backend and
           vice-versa making it very flexible for implementing virtual
           directories, proxy servers and gateways to X.500.
         </li>
         
         <li>
-          Several backends can be implemented and plugged into Eve's partition
-          nexus.  Eve will initially support a BTree based partition but any
-          backing store can be used to implement a partition so long as it
-          conforms to interfaces.
+          Several backends can be implemented and plugged into the server's
+          partition nexus.  The server supports a BTree based partition out of
+          the box but any backing store can be used to implement a partition so
+          long as it conforms to interfaces.
         </li>
         
         <li>
-          Eve will expose all aspects of administration via a special system
+          The server exposes all aspects of administration via a special system
           backend.  LDAP can be used to manage these concerns through the
           system naming context at <code>ou=system</code>.
         </li>
@@ -46,36 +46,37 @@
         </li>
         
         <li>
-          Both Eve's backend subsystem and her frontend are separable and
+          Both the backend subsystem and the frontend are separable and
           independently embeddable.
         </li>
         
         <li>
-          Eve implements a server side JNDI LDAP provider as the facade for the 
-          entire backend subsystem.  JNDI operations are directly translated by
-          this provider into operations against the nexus and the target 
-          partitions storing the entries.
+          The server contains a server side JNDI LDAP provider as the facade
+          for the entire backend subsystem.  JNDI operations are directly
+          translated by this provider into operations against the nexus and the
+          target partitions storing server entries.
         </li>
         
         <li>
-          Eve will use JNDI as the data access API for stored procedures.  This
-          makes stored procedures functional within and outside of the server
-          without requiring recompilation.
+          The server will use JNDI as the data access API for stored procedures.
+          This will make stored procedures functional within and outside of the
+          server without requiring recompilation.
         </li>
         
         <li>
-          Eve's networking code is based on a simple Staged Event Driven
-          Architecture (SEDA) which gives Eve the ability to handle large
+          The server's networking code is based on a simple Staged Event Driven
+          Architecture (SEDA) which gives it the ability to handle large
           amounts of concurrency.  Multiple swapable network layers will be
           available for different usage characteristics.
         </li>
         
         <li>
-          Eve uses the Snickers tools and APIs for ASN.1 BER encoding and 
+          The server uses the Snickers tools and APIs for ASN.1 BER encoding and
           decoding.  These tools are designed for a very small encoding and
           decoding footprint as well as for use in non-blocking servers.  The
-          chunking nature of the BER codec makes Eve very efficient at handling
-          this aspect of the protocol and makes her resistant to DoS attacks.
+          chunking nature of the BER codec makes the server very efficient while
+          handling encoding and decoding making it more resistant to DoS
+          attacks.
         </li>
       </ul>
       </section>

Modified: incubator/directory/server/trunk/xdocs/index.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/index.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/index.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/index.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/index.xml	(original)
+++ incubator/directory/server/trunk/xdocs/index.xml	Fri Jan  7 15:24:55 2005
@@ -2,17 +2,18 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Directory Server</title>
+    <title>Apache Directory Server</title>
   </properties>
   
   <body>
     <section name="Overview">
-      <p>Welcome to the Eve Directory Server Homepage!</p>
+      <p>Welcome to the Apache Directory Server Homepage!</p>
 
       <p>
-        Eve is an embeddable LDAP server written in Java.  It has been designed
-        to introduce triggers, stored procedures, queues and views to the world
-        of LDAP which has lacked these rich constructs.
+        The Apache Directory Server is an embeddable LDAP server written in
+        Java.  It has been designed to introduce triggers, stored procedures,
+        queues and views to the world of LDAP which has lacked these rich
+        constructs.
       </p>
       
       <table>
@@ -35,7 +36,7 @@
             <a href="./roadmap.html">Roadmap</a>
           </td>
           <td>
-            A roadmap for Eve development.
+            A development roadmap.
           </td>
         </tr>
 
@@ -59,7 +60,7 @@
 
         <tr>
           <td>
-            <a href="./projects/index.html">Eve Projects</a>
+            <a href="./projects/index.html">Projects</a>
           </td>
           <td>
             The sitedocs for the various maven source code projects containing

Modified: incubator/directory/server/trunk/xdocs/mailing-lists.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/mailing-lists.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/mailing-lists.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/mailing-lists.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/mailing-lists.xml	(original)
+++ incubator/directory/server/trunk/xdocs/mailing-lists.xml	Fri Jan  7 15:24:55 2005
@@ -23,7 +23,7 @@
         </thead>
         <tbody>
           <tr>
-            <td>Apache Directory Developement - use [eve] prefix</td>
+            <td>Apache Directory Developement - use [server] prefix</td>
             <td>
               <a href="mailto:directory-dev-subscribe@incubator.apache.org">Subscribe</a>
             </td>

Modified: incubator/directory/server/trunk/xdocs/navigation.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/navigation.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/navigation.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/navigation.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/navigation.xml	(original)
+++ incubator/directory/server/trunk/xdocs/navigation.xml	Fri Jan  7 15:24:55 2005
@@ -8,9 +8,6 @@
 
     <links>
       <item name="Directory" href="../../index.html"/>
-      <!--
-      <item name="Eve" href="../eve/index.html"/>
-      -->
       <item name="LDAP" href="../directory-ldap/index.html"/>
       <item name="Naming" href="../directory-naming/index.html"/>
       <item name="ASN.1" href="../asn1/index.html"/>
@@ -19,7 +16,7 @@
       <item name="SEDA" href="../seda/index.html"/>
     </links>
 
-    <menu name="Eve">
+    <menu name="Apache Directory Server">
       <item name="Overview" href="/index.html"/>
       <item name="Features" href="/features.html"/>
       <item name="Roadmap" href="/roadmap.html"/>
@@ -37,19 +34,19 @@
         <item name="Protocol" href="/developers/protocol.html"/>
         <item name="Backend Subsystem" href="/developers/backend.html"/>
       </item>
-      <item name="Eve Projects" href="/projects/index.html" collapse="true">
-        <item name="main" href="/projects/eve/index.html"/>
-        <item name="core" href="/projects/eve-dib/index.html"/>
-        <item name="shared" href="/projects/eve-shared/index.html"/>
-        <item name="protocol" href="/projects/eve-protocol/index.html"/>
-        <item name="plugin" href="/projects/maven-eve-plugin/index.html"/>
+      <item name="Server Projects" href="/projects/index.html" collapse="true">
+        <item name="main" href="/projects/server-main/index.html"/>
+        <item name="core" href="/projects/server-core/index.html"/>
+        <item name="shared" href="/projects/server-shared/index.html"/>
+        <item name="protocol" href="/projects/server-protocol/index.html"/>
+        <item name="plugin" href="/projects/maven-directory-plugin/index.html"/>
       </item>
     </menu>
     
     <menu name="Project Information">
       <item name="Wiki" href="http://wiki.apache.org/directory"/>
-      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIREVE"/>
-      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/?root=Apache-SVN"/>
+      <item name="Open Issues" href="http://issues.apache.org/jira/browse/DIRSERVER"/>
+      <item name="Source Repositories" href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/?root=Apache-SVN"/>
       <item name="Mailing Lists" href="/mailing-lists.html"/>
       <item name="License" href="/license.html"/>
       <item name="Notices" href="/notices.html"/>

Modified: incubator/directory/server/trunk/xdocs/projects/index.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/projects/index.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/projects/index.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/projects/index.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/projects/index.xml	(original)
+++ incubator/directory/server/trunk/xdocs/projects/index.xml	Fri Jan  7 15:24:55 2005
@@ -2,14 +2,14 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Projects</title>
+    <title>Server Projects</title>
   </properties>
   
   <body>
-    <section name="Eve Projects">
+    <section name="Server Projects">
       <p>
-        Eve is composed of several Maven projects.  The usually Maven generated
-        project documenation for each of them can be accessed here:
+        The server is composed of several Maven projects.  The usually Maven
+        generated project documenation for each of them can be accessed here:
       </p>
       
       <table>
@@ -20,29 +20,30 @@
         
         <tr>
           <td>
-            <a href="../projects/eve/index.html">main</a>
+            <a href="../projects/server/index.html">main</a>
           </td>
           <td>
-            Eve command line server application with <code>main()</code>
+            Command line server application with <code>main()</code>
           </td>
         </tr>
 
         <tr>
           <td>
-            <a href="../projects/eve-core/index.html">core</a>
+            <a href="../projects/server-core/index.html">core</a>
           </td>
           <td>
-            Eve's core contains all of Eve's backend subsystems.  It depends on
-            protocol and uses it with seda to service LDAP requests.  The core
-            contains the JNDI provider, interceptor framework, interceptor 
-            services, the schema subsystem and the database subsystem.  Hence 
-            the core is the heart of the server as its name suggests.
+            The server's core contains all of it's backend subsystems.  The
+            core depends on the protocol and uses it with seda to service LDAP
+            requests.  The core contains the JNDI provider, interceptor
+            framework, interceptor services, the schema subsystem and the
+            database subsystem.  Hence the core is the heart of the server as
+            its name suggests.
           </td>
         </tr>
 
         <tr>
           <td>
-            <a href="../projects/eve-shared/index.html">shared</a>
+            <a href="../projects/server-shared/index.html">shared</a>
           </td>
           <td>
             Code shared by the core and plugin separated to prevent cyclic deps
@@ -51,19 +52,19 @@
 
         <tr>
           <td>
-            <a href="../projects/eve-protocol/index.html">protocol</a>
+            <a href="../projects/server-protocol/index.html">protocol</a>
           </td>
           <td>
-            Eve's LDAP Protocol Provider
+            The server's LDAP Protocol Provider
           </td>
         </tr>
 
         <tr>
           <td>
-            <a href="../projects/maven-eve-plugin/index.html">plugin</a>
+            <a href="../projects/maven-directory-plugin/index.html">plugin</a>
           </td>
           <td>
-            Eve's Maven Plugin
+            The server's Maven Plugin
           </td>
         </tr>
       </table>

Modified: incubator/directory/server/trunk/xdocs/roadmap.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/roadmap.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/roadmap.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/roadmap.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/roadmap.xml	(original)
+++ incubator/directory/server/trunk/xdocs/roadmap.xml	Fri Jan  7 15:24:55 2005
@@ -2,11 +2,11 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Roadmap</title>
+    <title>Server Roadmap</title>
   </properties>
   
   <body>
-    <section name="Eve Roadmap">
+    <section name="Server Roadmap">
       <p>
         Until we pull this together over here in a nice format you can get an
         idea of what is going on using these alternative sources of info:

Modified: incubator/directory/server/trunk/xdocs/users/authentication.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/authentication.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/authentication.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/authentication.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/authentication.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/authentication.xml	Fri Jan  7 15:24:55 2005
@@ -2,17 +2,17 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve Authentication</title>
+    <title>Server Authentication</title>
   </properties>
   
   <body>
 
-    <section name="Eve Authentication">
+    <section name="Server Authentication">
       <subsection name="Status">
         <p>
-          Presently Eve supports only simple authentication and anonymous binds
-          while storing passwords as clear text within userPassword attributes
-          in user entries.
+          Presently the directory server supports only simple authentication
+          and anonymous binds while storing passwords in clear text within
+          userPassword attributes in user entries.
         </p>
 
         <p>
@@ -26,16 +26,16 @@
 
       <subsection name="What password do I use?">
         <p>
-          So you just downloaded Eve and fired her up.  Now you're wondering how
-          to get an LDAP client like jxplorer, gq, or ldapbrowser to bind to the
-          server over the wire.
+          So you just downloaded the server and fired her up.  Now you're
+          wondering how to get an LDAP client like jxplorer, gq, or ldapbrowser
+          to bind to the server over the wire.
         </p>
 
         <p>
           By default the super user or admin account is created when the system
           partition is created under the ou=system naming context.  This occurs
-          when Eve is started for the first time.  The admin user can be found
-          under the following DN:
+          when the server is started for the first time.  The admin user can be
+          found under the following DN:
         </p>
 
         <source>
@@ -57,13 +57,13 @@
 
       <subsection name="Adding and authenticating normal users">
         <p>
-          A user in Eve is any entry with a userPassword attribute that contains
-          a clear text password.  The DN can be anything reachable within one of
-          the directory partitions.  So if you add a partition to hang off of
-          <code>dc=example,dc=com</code> then you can add user entries anywhere
-          under this naming context or just add user entries under the
-          <code>ou=system</code> naming context.  Above is an LDIF of a user
-          you can add to the directory as a test user.
+          A user in the server is any entry with a userPassword attribute that
+          contains a clear text password.  The DN can be anything reachable
+          within one of the directory partitions.  So if you add a partition to
+          hang off of <code>dc=example,dc=com</code> then you can add user
+          entries anywhere under this naming context or just add user entries
+          under the <code>ou=system</code> naming context.  Above is an LDIF of
+          a user you can add to the directory as a test user.
         </p>
 
         <source>
@@ -123,16 +123,17 @@
 
       <subsection name="Protecting User Passwords">
         <p>
-          Eve at the moment has a sweet spot for new users.  This sweet
+          At the moment there's a sweet spot for new users.  This sweet
           spot is immediately under the ou=users,ou=system context.  Users
-          created here are hard protected right now.  Eve does not have a formal
-          authorization mechanism in place yet to protect entries from other
-          users.  Authorization rules have been hardcoded into the system for
-          now to control access to user entries under <code>ou=users,ou=system
-          </code>.  Only the admin and the user him/her self can access their
-          entry for reads.  Users cannot modify their group membership
-          properties but can change their own passwords.  They do not see each
-          other at all.  The admin can read and write anything.
+          created here are hard protected right now.  The server does not have
+          a formal authorization mechanism in place yet to protect entries from
+          other users.  Authorization rules have been hardcoded into the system
+          for now to control access to user entries under <code>ou=users,
+          ou=system</code>.  Only the admin and the user him/her self can
+          access their entries for reads.  Users cannot modify their group
+          membership properties but can change their own passwords.  They do
+          not see each other's accounts at all.  The admin is the only one that
+          can read and write anything.
         </p>
 
         <p>
@@ -142,12 +143,12 @@
         </p>
 
         <p>
-          Note that anonymous binds and binds as other users show different
+          Note that anonymous binds and binds as users show different
           views of the ou=system naming context.  So don't freak out if you
           don't see the usual suspects when binding anonymously!  Anonymous
           users cannot see the admin account or any other user accounts.  Users
           other than admin cannot see the admin account and can only see one
-          user account: their own.  The admin see everything and can alter or
+          user account: their own.  The admin sees everything and can alter or
           remove any entry.
         </p>
       </subsection>
@@ -155,13 +156,13 @@
       <subsection name="Disabling Anonymous Binds">
         <p>
           Anonymous binds come enabled out of the box.  So you might want to
-          turn off this feature especially when you cannot protect much of
+          turn off this feature especially since you cannot protect much of
           your data at the present moment from access using authorization rules.
-          To do so you're going to have to restart Eve while disallowing these
-          binds.  The <b>eve.disable.anonymous</b> property when present as a
-          key in the enviroment (regardless of value) will disable access by
-          anonymous users.  This applies to authentication via LDAP clients
-          over the wire and via JNDI caller through the Eve JNDI provider.
+          To do so you're going to have to restart the server while disallowing
+          these binds.  The <b>server.disable.anonymous</b> property when
+          present as a key in the enviroment (regardless of value) will disable
+          access by anonymous users.  This applies to authentication via LDAP
+          clients over the wire and via JNDI caller through the JNDI provider.
         </p>
       </subsection>
 

Modified: incubator/directory/server/trunk/xdocs/users/building.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/building.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/building.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/building.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/building.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/building.xml	Fri Jan  7 15:24:55 2005
@@ -2,11 +2,11 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Building Eve</title>
+    <title>Apache Directory Project: Building the Directory Server</title>
   </properties>
   
   <body>
-    <section name="Building and Running Eve">
+    <section name="Building and Running the Apache Directory Server">
       <p>
         All directory projects use <a href="http://maven.apache.org">Maven</a>
         as the default build tool.  We try to remain current with the production
@@ -14,9 +14,9 @@
       </p>
 
       <p>
-        The multiproject plugin is used to build Eve.  After checking out the
-        Eve trunk from subversion, cd into it and run the following multiproject
-        command:
+        The multiproject plugin is used to build all the maven projects
+        associated with the server.  After checking out the server trunk from
+        subversion, cd into it and run the following multiproject command:
       </p>
 
       <source>
@@ -25,38 +25,38 @@
 
       <p>
         Once you've built the server you'll find an executable jar file under
-        the main/target directory labeled eve-${version}.jar which can be fired
-        up like so:
+        the main/target directory labeled server-main-${version}.jar which can
+        be fired up like so:
       </p>
 
 <source>
-[akarasulu@newton trunk]$ java -jar main/target/eve-0.8.0-SNAPSHOT.jar
-Eve: using default properties ...
-Eve: standard ldap port 389 is not available, using 1024 instead
-Eve: started in 1368 milliseconds
+[akarasulu@newton trunk]$ java -jar main/target/server-main-0.8.0-SNAPSHOT.jar
+server: using default properties ...
+server: standard ldap port 389 is not available, using 1024 instead
+server: started in 1368 milliseconds
 </source>
 
       <p>
         When you start the server without a properties file arguement default
-        settings are used.  She tries to bind to 389 but this non-root user
-        does not have the needed privledges so Eve tries to bind on the next
+        settings are used.  It tries to bind to 389 but this non-root user
+        does not have the needed privledges so it tries to bind on the next
         available port which is 1024.  If you would like a properties file can
-        be used to override and set Eve specific properties to control her
-        behavoir.  Below we use the <a href="http://wisdeant.notlong.com/">
+        be used to override and set server specific properties to control her
+        behavoir.  Below we use the <a href="http://vortuoad.notlong.com/">
         properties</a> file that comes preconfigured for Apache under the
-        eve/trunk/main directory:
+        server/trunk/main directory:
       </p>
 
 <source>
-[akarasulu@newton trunk]$ java -jar main/target/eve-0.8.0-SNAPSHOT.jar main/eve.properties
-Eve: loading properties from main/eve.properties
-Eve: started in 1449 milliseconds
+[akarasulu@newton trunk]$ java -jar main/target/server-main-0.8.0-SNAPSHOT.jar main/server.properties
+server: loading properties from main/eve.properties
+server: started in 1449 milliseconds
 </source>
     </section>
 
-    <section name="Eve's Maven Modules">
+    <section name="Apache Directory Server's Maven Modules">
       <p>
-        Eve is composed of 4 separate maven projects.  These projects are
+        The server is composed of 4 separate maven projects.  These projects are
         summarized below:
       </p>
 
@@ -71,18 +71,14 @@
         </tr>
         <tr>
           <td>plugin</td>
-          <td>Contains a maven plugin used while developing with/for Eve.</td>
+          <td>Contains a maven plugin used while developing with/for the
+              directory server.</td>
         </tr>
         <tr>
-          <td>dib</td>
+          <td>core</td>
           <td>
-            Contains Eve's DIB (Directory Information Base) which contains the
-            JNDI Provider that wraps/is the backend subsystem.  This name DIB
-            is really a misnomer: the DIB in X.500 terms represents collectively
-            the distributed database of all the entries in a directory system
-            composed of one or more servers.  We just use it cuz it's 3 letters
-            long and we did not know whether we should call it backend, or
-            database, or what.
+            Contains the server's core which contains the JNDI Provider that
+            wraps/is the backend subsystem.
           </td>
         </tr>
         <tr>
@@ -93,12 +89,12 @@
           <td>optional</td>
           <td>
             We might create this project in the near future to contain bundles
-            of optional schema jars.  Eve's maven plugin generates Java class
-            files for OpenLDAP schema files.  These classes create schema
+            of optional schema jars.  The server's maven plugin generates Java
+            class files for OpenLDAP schema files.  These classes create schema
             objects way faster than parsing a file to dynamically create schema
             objects.  The optional package will contain all the schema classes
-            for published schemas we can find.  When firing up Eve you can
-            request to load only those schemas you actually use.
+            for published schemas we can find.  When firing up the server you
+            can request to load only those schemas you actually use.
           </td>
         </tr>
       </table>

Modified: incubator/directory/server/trunk/xdocs/users/deploying.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/deploying.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/deploying.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/deploying.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/deploying.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/deploying.xml	Fri Jan  7 15:24:55 2005
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Building Eve</title>
+    <title>Apache Directory Project: Deploying the Server</title>
   </properties>
   
   <body>
@@ -20,7 +20,7 @@
       </ul>
     </section>
 
-    <section name="Deploying Eve">
+    <section name="Deploying the Server">
       <p>
         Coming later ...
       </p>

Modified: incubator/directory/server/trunk/xdocs/users/index.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/index.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/index.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/index.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/index.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/index.xml	Fri Jan  7 15:24:55 2005
@@ -2,15 +2,15 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve User's Guide</title>
+    <title>User's Guide</title>
   </properties>
   
   <body>
     <section name="User's Guide">
       <p>
         Here we have assembled a bunch of guides and howto like documents that
-        demonstrate how Eve can be used.  Hopefully this will grow into a user's
-        guide.
+        demonstrate how the server can be used.  Hopefully this will grow into
+        a user's guide.
       </p>
 
       <table>
@@ -24,7 +24,7 @@
             <a href="./building.html">Building</a>
           </td>
           <td>
-            Shows how to build Eve from the repository.
+            Shows how to build the directory server from the repository.
           </td>
         </tr>
 
@@ -33,7 +33,8 @@
             <a href="./authentication.html">Authentication</a>
           </td>
           <td>
-            Demonstrates how to bind to the server as admin and setup other user accounts.
+            Demonstrates how to bind to the server as admin and setup other
+            user accounts.
           </td>
         </tr>
 
@@ -63,7 +64,7 @@
           </td>
           <td>
             Lists the goals, properties and the steps required to integrate
-            your project with the Maven Plugin for Eve.
+            your project with the Maven Plugin for the directory server.
           </td>
         </tr>
 

Modified: incubator/directory/server/trunk/xdocs/users/jndi.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/jndi.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/jndi.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/jndi.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/jndi.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/jndi.xml	Fri Jan  7 15:24:55 2005
@@ -2,52 +2,54 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Eve JNDI Provider</title>
+    <title>Server-Side JNDI Provider</title>
   </properties>
   
   <body>
-    <section name="Eve JNDI Provider">
+    <section name="Server-Side JNDI Provider">
       <p>
-        Besides an LDAP protocol server, Eve is also a JNDI provider for the
-        LDAP namespace.  Unlike the SUN JNDI LDAP Provider which is an LDAP
-        client, the Eve JNDI Provider is not.  JNDI operations on Contexts
-        directly tap into the server's database partitions to add, lookup,
-        alter, and search for entries.  There is nothing done over the wire.
+        The Apache Directory Server contains a JNDI provider for the LDAP
+        namespace.  Unlike the SUN JNDI LDAP Provider which is an LDAP
+        client, the Server-Side JNDI Provider is not.  JNDI operations on
+        Contexts directly tap into the server's database partitions to add,
+        lookup, alter, and search for entries.  There is nothing done over the
+        wire.
       </p>
 
       <p>
-        Eve leverages its JNDI LDAP provider in several ways.  First stored
-        procedures written in Java will naturally use JNDI to alter entries
-        using this provider.  Thanks to JNDI the same procedure outside of the
-        server can be tested using the SUN JNDI LDAP provider.  This
-        transparency is wicked cool making testing easy.  The Eve JNDI provider
-        is also used as the API of choice for integrating Eve into other Java
-        applications and servers.  The first InitialContext request to the Eve
-        provider fires up the entire server.  So you need not learn anything
-        new to start playing with her!
+        The server leverages its server side JNDI LDAP provider in several ways.
+        First stored procedures written in Java will naturally use JNDI to
+        alter entries using this provider.  Thanks to JNDI the same procedure
+        outside of the server can be tested using the SUN JNDI LDAP provider.
+        This transparency is wicked cool since it makes testing easy.  The
+        server side JNDI provider is also used as the API of choice for
+        integrating the server into other Java applications and servers.  The
+        first InitialContext request to the server side provider fires up the
+        entire server.  So you need not learn anything new to start using and
+        embedding the Apache Directory Server!
       </p>
 
       <p>
-        This document describes the Eve JNDI Provider in terms of the custom
-        properties used to control its behavoir in the solid state and for
-        configuring her on start up.
+        This document describes the server side JNDI Provider in terms of the
+        custom properties used to control its behavoir in the solid state and
+        for configuring the server on start up.
       </p>
     </section>
 
-    <section name="Eve Specific JNDI Properties">
+    <section name="Server Specific JNDI Properties">
       <table>
         <tr><th>key</th><th>optional</th><th>description</th></tr>
         <tr>
-          <td>eve.wkdir</td>
+          <td>server.wkdir</td>
           <td>true</td>
           <td>
-            The file system directory Eve will use as its working directory to
-            store database files and other things.
+            The file system folder the server will use to store database files
+            and other things.
           </td>
         </tr>
 
         <tr>
-          <td>eve.schemas</td>
+          <td>server.schemas</td>
           <td>true</td>
           <td>
             The schema configuration settings.
@@ -55,7 +57,7 @@
         </tr>
 
         <tr>
-          <td>eve.disable.anonymous</td>
+          <td>server.disable.anonymous</td>
           <td>true</td>
           <td>
             If present disables anonymous binds.
@@ -63,7 +65,7 @@
         </tr>
 
         <tr>
-          <td>eve.operation.sync</td>
+          <td>server.operation.sync</td>
           <td>true</td>
           <td>
             If present when requesting an InitialContext this property forces
@@ -72,7 +74,7 @@
         </tr>
 
         <tr>
-          <td>eve.operation.shutdown</td>
+          <td>server.operation.shutdown</td>
           <td>true</td>
           <td>
             If present when requesting an InitialContext this property
@@ -84,7 +86,7 @@
 
 
         <tr>
-          <td>eve.net.disable.protocol</td>
+          <td>server.net.disable.protocol</td>
           <td>true</td>
           <td>
             Used when starting up the server to disable the networking frontend
@@ -93,7 +95,7 @@
         </tr>
 
         <tr>
-          <td>eve.net.passthru</td>
+          <td>server.net.passthru</td>
           <td>true</td>
           <td>
             Used to pass an existing network frontend to the server rather
@@ -102,7 +104,7 @@
         </tr>
 
         <tr>
-          <td>eve.net.ldap.port</td>
+          <td>server.net.ldap.port</td>
           <td>true</td>
           <td>
             The LDAP port to use for servicing LDAP protocol requests if not
@@ -111,7 +113,7 @@
         </tr>
 
         <tr>
-          <td>eve.net.ldaps.port</td>
+          <td>server.net.ldaps.port</td>
           <td>true</td>
           <td>
             The LDAP port to use for servicing secure LDAP protocol requests if
@@ -120,7 +122,7 @@
         </tr>
 
         <tr>
-          <td>eve.db.partitions</td>
+          <td>server.db.partitions</td>
           <td>true</td>
           <td>
             The list of database partition identifiers.
@@ -128,7 +130,7 @@
         </tr>
 
         <tr>
-          <td>eve.db.partition.suffix.</td>
+          <td>server.db.partition.suffix.</td>
           <td>false when adding partitions</td>
           <td>
             A key base for listing the suffixes of database partitions.  The
@@ -138,7 +140,7 @@
         </tr>
 
         <tr>
-          <td>eve.db.partition.indices.</td>
+          <td>server.db.partition.indices.</td>
           <td>true</td>
           <td>
             A key base for listing the indices for database partitions.  The
@@ -148,7 +150,7 @@
         </tr>
 
         <tr>
-          <td>eve.db.partition.attributes.</td>
+          <td>server.db.partition.attributes.</td>
           <td>false when adding partitions</td>
           <td>
             A key base for listing the attributes and values for the suffix
@@ -163,28 +165,29 @@
       </table>
     </section>
 
-    <section name="Embedding Eve">
+    <section name="Embedding the Apache Directory Server">
       <p>
-        Embedding Eve is really easy.  Just set the JNDI initial context
-        factory and other security settings along with Eve specific properties
-        to fire her up.  Here's a simple example of code that embeds Eve using
-        the minimum configuration information:
+        Embedding the server is really easy.  Just set the JNDI initial context
+        factory and other security settings along with specific properties
+        to fire her up.  Here's a simple example of code that embeds the server
+        using the minimum configuration information:
       </p>
 
 <source>
 Hashtable env = new Hashtable();
 env.setProperty( Context.PROVIDER_URL, "ou=system" );
-env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.apache.eve.jndi.EveContextFactory" );
+env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.apache.ldap.server.jndi.ServerContextFactory" );
 InitialDirContext ctx = new InitialDirContext( env );
 </source>
 
       <p>
-        This code snippet starts up Eve on port 389 or the next available port.
-        There is only one partition in the system hanging off of the "ou=system"
-        naming context.  The server allows for anonymous binds and has two users
-        preconfigured: a regular test user, <b>uid=akarasulu,ou=users,ou=system
-        </b> with password <i>test</i>, and the super user <b>uid=admin,ou=system
-        </b>, with password <i>secret</i>.
+        This code snippet starts up the server on port 389 or the next
+        available port if access to 389 is denied or another server is already
+        bound to that port.  There is only one partition in the system hanging
+        off of the "ou=system" naming context.  The server allows for anonymous
+        binds and has two users preconfigured: a regular test user,
+        <b>uid=akarasulu,ou=users,ou=system</b> with password <i>test</i>, and
+        the super user <b>uid=admin,ou=system</b>, with password <i>secret</i>.
       </p>
 
       <p>
@@ -201,7 +204,7 @@
 
 // Standard JNDI properties
 env.setProperty( Context.PROVIDER_URL, "ou=system" );
-env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.apache.eve.jndi.EveContextFactory" );
+env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.apache.ldap.server.jndi.ServerContextFactory" );
 env.setProperty( Context.SECURITY_PRINCIPAL, "uid=admin,ou=system" );
 env.setProperty( Context.SECURITY_CREDENTIALS, "secret" );
 env.setProperty( Context.SECURITY_PRINCIPAL, "uid=admin,ou=system" );
@@ -232,7 +235,7 @@
 
       <p>
         This configuration starts up the server on port 10389 with anonymous
-        binds disabled.  Eve stores its database files under /var/ldap
+        binds disabled.  The server stores its database files under /var/ldap
         and creates a new application partition for Apache entries off of the
         <b>dc=apache,dc=org</b> naming context in addition to the system
         partition.  If you look closely at /var/ldap you'll see a directory

Modified: incubator/directory/server/trunk/xdocs/users/partitions.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/partitions.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/partitions.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/partitions.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/partitions.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/partitions.xml	Fri Jan  7 15:24:55 2005
@@ -16,10 +16,10 @@
 
       <subsection name="Status">
         <p>
-          Presently Eve has a single partition implementation which is used for
-          both the system partition and user partitions.  It uses
-          <a href="http://jdbm.sourceforge.net/">JDBM</a> as the underlying
-          B+Tree implementation for storing entries.
+          Presently the server has a single partition implementation.  This
+          implementation is used for both the system partition and user
+          partitions.  It uses <a href="http://jdbm.sourceforge.net/">JDBM</a>
+          as the underlying B+Tree implementation for storing entries.
         </p>
 
         <p>
@@ -31,8 +31,8 @@
         <p>
           Partitions have simple interfaces that can be used to align any data
           source to the LDAP data model thereby accessing it via JNDI or via
-          LDAP over the wire.  This makes Eve very flexible as a bridge to
-          standardize access to disparate data sources and formats.  Dynamic
+          LDAP over the wire.  This makes the server very flexible as a bridge
+          to standardize access to disparate data sources and formats.  Dynamic
           mapping based backends are also interesting.
         </p>
       </subsection>
@@ -46,31 +46,33 @@
         </p>
 
         <p>
-          Eve's subsystems will use this partition to store information critical
-          to their operation.  Things like triggers, stored procedures, access
-          control instructions and schema information can be maintained here.
+          The server's subsystems will use this partition to store information
+          critical to their operation.  Things like triggers, stored procedures,
+          access control instructions and schema information can be maintained
+          here.
         </p>
       </subsection>
 
       <subsection name="Root Nexus">
         <p>
           Several partitions can be assigned to different naming contexts within
-          Eve so long as their names do not overlap such that one partition's
-          naming context is contained within anothers.  The root nexus is a fake
-          partition that does not really store entries.  It maps other entry
-          storing partitions to naming contexts and routes backing store calls
-          to the partition containing the entry associated with the operation.
+          the server so long as their names do not overlap such that one
+          partition's naming context is contained within anothers.  The root
+          nexus is a fake partition that does not really store entries.  It maps
+          other entry storing partitions to naming contexts and routes backing
+          store calls to the partition containing the entry associated with the
+          operation.
         </p>
       </subsection>
 
       <subsection name="User Partitions">
         <p>
           User partitions are partitions added by users.  When you download and
-          start using Eve you may want to create a separate partition to store
-          the entries of your application.  To us user (sometimes also referred
-          to as application) partitions are those that are not the system
+          start using the server you may want to create a separate partition to
+          store the entries of your application.  To us user (sometimes also
+          referred to as application) partitions are those that are not the system
           partition!  In the following section we describe how a user partition
-          can be created in Eve.
+          can be created in the server.
         </p>
       </subsection>
     </section>
@@ -88,7 +90,7 @@
         <p>
           Obviously properties files are not the best way to configure a large
           system like an LDAP server.  However properties files are the JNDI
-          standard for pulling in configuration.  Eve as a JNDI provider tries
+          standard for pulling in configuration.  The server's JNDI provider tries
           to honor this.  Hence the use of a properties file for configuration.
           Below we have the configuration of two user defined partitions within
           a properties file.  These partitions are for the naming contexts:
@@ -97,37 +99,38 @@
 
     <source>
 # all multivalued properties are space separated like the list of partions here
-eve.db.partitions=apache test
+server.db.partitions=apache test
 
 # apache partition configuration
-eve.db.partition.suffix.apache=dc=apache,dc=org
-eve.db.partition.indices.apache=ou cn objectClass uid
-eve.db.partition.attributes.apache.dc=apache
-eve.db.partition.attributes.apache.objectClass=top domain extensibleObject
+server.db.partition.suffix.apache=dc=apache,dc=org
+server.db.partition.indices.apache=ou cn objectClass uid
+server.db.partition.attributes.apache.dc=apache
+server.db.partition.attributes.apache.objectClass=top domain extensibleObject
 
 # test partition configuration
-eve.db.partition.suffix.test=ou=test
-eve.db.partition.indices.test=ou objectClass
-eve.db.partition.attributes.test.ou=test
-eve.db.partition.attributes.test.objectClass=top organizationalUnit extensibleObject
+server.db.partition.suffix.test=ou=test
+server.db.partition.indices.test=ou objectClass
+server.db.partition.attributes.test.ou=test
+server.db.partition.attributes.test.objectClass=top organizationalUnit extensibleObject
     </source>
 
         <p>
-          Although somewhat ugly the way we use properties for settings does
-          work.  Hopefully we can build a tool on top of this to save the
-          user some hassle.  Another approach may be to use XML or something
-          easier to generate these properties from them.  For now its the best
-          non-specific means we have to inject settings through JNDI environment
-          Hashtables while still being able to load settings via properties
-          files.  Properties from proerties files are the common denominator
-          though.  Another means is however possible programatically.
+          Although somewhat ugly the way we use properties for settings is
+          portable across JNDI LDAP providers.  Hopefully we can build a tool
+          on top of this to save the user some hassle.  Another approach may be
+          to use XML or something easier to generate these properties from them.
+          For now its the best non-specific (to the server's provider) means we
+          have to inject settings through JNDI environment Hashtables while
+          still being able to load settings via properties files.  Properties
+          from proerties files are the common denominator though.  Another
+          easier means to configure the server is possible programatically.
         </p>
         <h3>Partition Id</h3>
         <p>
           Breifly we'll explain these properties and the scheme used.  A
           partition's property set is associated as a set using the partition's
           id.  All partition ids are listed as a space separated list using the
-          <b>eve.db.partitions</b> property: above it lists the ids for the two
+          <b>server.db.partitions</b> property: above it lists the ids for the two
           partitions, <i>apache</i> and <i>test</i>.
         </p>
         <h3>Naming Context</h3>
@@ -137,19 +140,20 @@
           entries in the partition have this common suffix.  The suffix is a
           distinguished name.  The property key for the suffix of a partition is
           composed of the following property key base
-          <b>eve.db.partition.suffix.</b> concatenated with the id of the
-          partition: <b>eve.db.partition.suffix.</b><i>${id}</i>.  For example
+          <b>server.db.partition.suffix.</b> concatenated with the id of the
+          partition: <b>server.db.partition.suffix.</b><i>${id}</i>.  For example
           if the partition id is foo, then the suffix key would be,
-          <b>eve.db.partition.suffix.foo</b>.
+          <b>server.db.partition.suffix.foo</b>.
         </p>
         <h3>User Defined Indices</h3>
         <p>
           Partitions can have indices on attributes.  Unlike OpenLDAP where you
-          can build specific types of indices, Eve indices are of a single type.
-          For each partition a key is assembled from the partition id and the
-          property key base: <b>eve.db.partition.indices.</b><i>${id}</i>.  So
+          can build specific types of indices, the server's indices are of a
+          single type.  For each partition, a key is assembled from the
+          partition id and the property key base:
+          <b>server.db.partition.indices.</b><i>${id}</i>.  So
           again for foo the key for attribute indices would be
-          <b>eve.db.partition.indices.foo</b>.  This value is a space separated
+          <b>server.db.partition.indices.foo</b>.  This value is a space separated
           list of attributeType names to index.  For example the apache
           partition has indices built on top of <b>ou</b>, <b>objectClass</b>
           and <b>uid</b>.
@@ -162,9 +166,9 @@
           specify these attributes as well as their values.  To do so we again
           use a key composed of a base, however this time we use both the id
           of the partition and the name of the attribute:
-          <b>eve.db.partition.attributes.</b><i>${id}</i>.<i>${name}</i>.  So
+          <b>server.db.partition.attributes.</b><i>${id}</i>.<i>${name}</i>.  So
           for partition foo and attribute bar the following key would be used:
-          <b>eve.db.partition.attributes.foo.bar</b>.    The value of the key
+          <b>server.db.partition.attributes.foo.bar</b>.    The value of the key
           is a space separated list of values for the bar attribute.  For
           example the apache partition's suffix has an objectClass attribute
           and its values are set to: top domain extensibleObject.
@@ -183,7 +187,7 @@
 
         <p>
           Simply put the Attributes into the Hashtable using the following
-          key <b>eve.db.partition.attributes.</b><i>${id}</i>.  Below we show
+          key <b>server.db.partition.attributes.</b><i>${id}</i>.  Below we show
           how this can be done for the same example above:
         </p>
 
@@ -221,9 +225,9 @@
         <p>
           Ok that does not look any shorter.  We'll add to this in the future.
           Perhaps we enable the use of configuration beans that can be used
-          with an SPI specific to Eve.  However this starts making your code
-          Eve specific.  You can just change properties and use the SUN provider
-          anymore to have your code be location independent.
+          with an SPI specific to server.  However this starts making your code
+          server provider specific.  You can just change properties and use the
+          SUN provider anymore to have your code be location independent.
         </p>
       </subsection>
     </section>
@@ -262,7 +266,7 @@
           <li>
             Partitions using other LDAP servers to store their entries.  Why
             do this when introducing latency.  Perhaps you want to proxy other
-            servers or make other servers behave like Eve.
+            servers or make other servers behave like the server.
           </li>
 
           <li>

Modified: incubator/directory/server/trunk/xdocs/users/plugin.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/server/trunk/xdocs/users/plugin.xml?view=diff&rev=124589&p1=incubator/directory/server/trunk/xdocs/users/plugin.xml&r1=124588&p2=incubator/directory/server/trunk/xdocs/users/plugin.xml&r2=124589
==============================================================================
--- incubator/directory/server/trunk/xdocs/users/plugin.xml	(original)
+++ incubator/directory/server/trunk/xdocs/users/plugin.xml	Fri Jan  7 15:24:55 2005
@@ -2,13 +2,13 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Maven Eve Plugin</title>
+    <title>Maven Directory Plugin</title>
   </properties>
   
   <body>
-    <section name="Maven Eve Plugin">
+    <section name="Maven Directory Plugin">
       <p>
-        Currently the primary function of the plugin is to generates Eve class
+        Currently the primary function of the plugin is to generates server class
         files for OpenLDAP schemas. These class files contain hard coded schema
         objects representing those found in the OpenLDAP files.  Why bother you
         may ask?  There are a few reasons for this:
@@ -47,7 +47,7 @@
             <th>Description</th>
           </tr>
           <tr>
-            <td>maven.eve.schema.target.dir</td>
+            <td>maven.ldap.server.schema.target.dir</td>
             <td>Yes</td>
             <td>
               <p>Default value is
@@ -55,7 +55,7 @@
             </td>
           </tr>
           <tr>
-            <td>maven.eve.schema.ownerDefault</td>
+            <td>maven.ldap.server.schema.ownerDefault</td>
             <td>Yes</td>
             <td>
               <p>Default value is
@@ -63,7 +63,7 @@
             </td>
           </tr>
           <tr>
-            <td>maven.eve.schema.dir</td>
+            <td>maven.ldap.server.schema.dir</td>
             <td>Yes</td>
             <td>
               <p>Default value is
@@ -71,11 +71,11 @@
             </td>
           </tr>
           <tr>
-            <td>maven.eve.schema.packageDefault</td>
+            <td>maven.ldap.server.schema.packageDefault</td>
             <td>Yes</td>
             <td>
               <p>Default value is
-                <code>org.apache.eve.schema.bootstrap</code>.</p>
+                <code>org.apache.ldap.server.schema.bootstrap</code>.</p>
             </td>
           </tr>
         </table>
@@ -83,27 +83,27 @@
 
       <goals>
         <goal>
-          <name>eve:generate</name>
+          <name>directory:generate</name>
           <description>
             Generates class files for OpenLDAP schemas.
           </description>
         </goal>
         <goal>
-          <name>eve:init</name>
+          <name>directory:init</name>
           <description>
             Finds the required parameters needed for the goals of the
             plugin.
           </description>
         </goal>
         <goal>
-          <name>eve:prepare-filesystem</name>
+          <name>directory:prepare-filesystem</name>
           <description>
             Creates source output directories used to deposite schema
             files that are generated.
           </description>
         </goal>
         <goal>
-          <name>eve:schema</name>
+          <name>directory:schema</name>
           <description>
             Top level schema generating function that uses other goals to
             coordinate generation.
@@ -113,8 +113,8 @@
 
       <subsection names="Usage">
         <p>
-           Take a look at how we integrate this into the Eve build 
-           <a href="http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/dib/">here</a>.
+           Take a look at how we integrate this into the directory server build
+           <a href="http://svn.apache.org/viewcvs.cgi/incubator/directory/server/trunk/core/">here</a>.
         </p>
       </subsection>
     </section>
@@ -130,29 +130,30 @@
       <ol>
         <li>
           Place your schema files (i.e. foo.schema) with the schema extension
-          into ${basedir}/src/schema.  If you opt to store it in another
-          location you must override the <code>maven.eve.schema.dir</code>
+          into ${basedir}/src/main/schema.  If you opt to store it in another
+          location you must override the <code>maven.ldap.server.schema.dir</code>
           property in your project.properties file.   For each schema file
-          add the file base name to the <code>maven.eve.schemas</code> property
-          which is a comma separated list.
+          add the file base name to the <code>maven.ldap.server.schemas</code>
+          property which is a space separated list.
         </li>
         <li>
           The plugin will by default generate java files within the
           ${basedir}/target/schema directory.  If you would like to
           generate code elsewhere you must override the <code>
-          maven.eve.schema.target.dir</code> property in your project.properties
-          file.
+          maven.ldap.server.schema.target.dir</code> property in your
+          project.properties file.
         </li>
         <li>
-          By default the plugin generates code in an Eve schema package:
-          <code>org.apache.eve.schema.bootstrap</code>.  If you want
+          By default the plugin generates code in a server schema package:
+          <code>org.apache.ldap.server.schema.bootstrap</code>.  If you want
           generated code for a schema to be put into a package other than this,
           then you're going to need to set the package property for the schema.
           The package property key is composed of the following base, <code>
-          maven.eve.schema.package.</code> with the name of the schema
+          maven.ldap.server.schema.package.</code> with the name of the schema
           (<b>without</b> the extension) appended to it.  So for schema file
           foo.schema the following property key would be used: <code>
-          maven.eve.schema.package.foo</code> where foo is the schema name.
+          maven.ldap.server.schema.package.foo</code> where foo is the schema
+          name.
         </li>
         <li>
           Using the same pattern above for all schema specific properties you
@@ -161,19 +162,20 @@
           others.  The schema dependency list is a comma separated list of other
           schema names.  These schemas need not be present in your project
           to generate the code for your schema.  The dependent schema classes
-          must however be present within Eve at deploy time in order to load and
-          use your schema.  At the end we list the the default schemas already
-          packaged into the Eve jar.  You can use any one of these schemas as
-          dependencies needed by your schema and not worry about their presence.
-          The property key <b>base</b> for the schema dependency list is <code>
-          maven.eve.schema.deps.</code> and for a foo.schema file the full key
-          would be <code>maven.eve.schema.deps.foo</code>
+          must however be present within the server at start up time in order to
+          load and use your schema.  At the end we list the the default schemas
+          already packaged into the server's jar.  You can use any one of these
+          schemas as dependencies needed by your schema and not worry about
+          their presence.  The property key <b>base</b> for the schema
+          dependency list is <code>maven.ldap.server.schema.deps.</code> and
+          for a foo.schema file the full key would be
+          <code>maven.ldap.server.schema.deps.foo</code>
         </li>
         <li>
           Each schema has an owner associated with it.  If you want the owner to
-          be anything other than the Eve super user you may want to set the
+          be anything other than the server's super user you may want to set the
           owner property for the schema in your project.properties file.  The
-          property key base for the schema is <code>maven.eve.schema.owner.
+          property key base for the schema is <code>maven.ldap.server.schema.owner.
           </code> so don't forget to append the schema name to it.
         </li>
       </ol>
@@ -183,30 +185,30 @@
       </p>
 
 <source>
-[akarasulu@newton dib]$ maven eve:schema
+[akarasulu@newton dib]$ maven directory:schema
  __  __
 |  \/  |__ _Apache__ ___
 | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
 |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
 
 Attempting to download ldap-common-0.8.0-SNAPSHOT.jar.
-Attempting to download eve-shared-0.8.0-SNAPSHOT.jar.
-Attempting to download eve-protocol-0.8.0-SNAPSHOT.jar.
+Attempting to download server-shared-0.8.0-SNAPSHOT.jar.
+Attempting to download server-protocol-0.8.0-SNAPSHOT.jar.
 Attempting to download snickers-codec-0.2.0-SNAPSHOT.jar.
 Attempting to download ldap-snickers-provider-0.8.0-SNAPSHOT.jar.
 Attempting to download snickers-ber-0.2.0-SNAPSHOT.jar.
 Attempting to download seda-0.2.0-SNAPSHOT.jar.
-Attempting to download maven-eve-plugin-0.8.0-SNAPSHOT.jar.
+Attempting to download maven-directory-plugin-0.8.0-SNAPSHOT.jar.
 Attempting to download ldap-common-0.8.0-SNAPSHOT.jar.
-Attempting to download eve-shared-0.8.0-SNAPSHOT.jar.
+Attempting to download server-shared-0.8.0-SNAPSHOT.jar.
 build:start:
 
-eve:schema:
-eve:init:
+directory:schema:
+directory:init:
 
-eve:prepare-filesystem:
+directory:prepare-filesystem:
 
-eve:generate:
+directory:generate:
     [echo] Generated schema producer classes for autofs.schema
     [echo] Generated schema producer classes for core.schema
     [echo] Generated schema producer classes for cosine.schema
@@ -218,19 +220,19 @@
     [echo] Generated schema producer classes for nis.schema
     [echo] Generated schema producer classes for system.schema
     [echo] Generated schema producer classes for scheduleworld.schema
-    [touch] Creating /home/akarasulu/projects/directory/eve/trunk/dib/target/schema/.flagfile
+    [touch] Creating /home/akarasulu/projects/directory/server/trunk/core/target/schema/.flagfile
 BUILD SUCCESSFUL
 Total time: 28 seconds
 Finished at: Tue Dec 14 15:26:26 EST 2004
 </source>
 
       <p>
-        The example above is from Eve.  If you would like to look at how to use
-        this plugin best the Eve <a href="http://figwarra.notlong.com/">
-        project.properties</a> file here is perhaps the best place to look.
-        Also from the output above you can see the schema files that are used
-        and packaged into Eve by default.  This may however change in the
-        future to restrict the set.
+        The example above is from the server's core project.  If you would like
+        to look at how to use this plugin best the server core
+        <a href="http://dumfount.notlong.com/">project.properties</a> file here
+        is perhaps the best place to look. Also from the output above you can
+        see the schema files that are used and packaged into the server by
+        default.  This may however change in the future to restrict the set.
       </p>
 
       <p>

Mime
View raw message