You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by er...@apache.org on 2011/04/08 13:43:05 UTC

svn commit: r1090212 - in /james/server/trunk/src/site/xdoc: dev.xml feature-persistence.xml feature-security.xml index.xml manage.xml

Author: eric
Date: Fri Apr  8 11:43:04 2011
New Revision: 1090212

URL: http://svn.apache.org/viewvc?rev=1090212&view=rev
Log:
Various content and format on server web site (JAMES-1219)

Modified:
    james/server/trunk/src/site/xdoc/dev.xml
    james/server/trunk/src/site/xdoc/feature-persistence.xml
    james/server/trunk/src/site/xdoc/feature-security.xml
    james/server/trunk/src/site/xdoc/index.xml
    james/server/trunk/src/site/xdoc/manage.xml

Modified: james/server/trunk/src/site/xdoc/dev.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/dev.xml?rev=1090212&r1=1090211&r2=1090212&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/dev.xml (original)
+++ james/server/trunk/src/site/xdoc/dev.xml Fri Apr  8 11:43:04 2011
@@ -52,9 +52,9 @@
     
     <p>The modules can be classified into 3 categories:</p>
     <ul>
-      <li>api: they does not include implementation details, they do not have dependencies (or at most they have very common dependencies like mailet-api, javamail, commons-logging).</li>
-      <li>library: they only depends on apis or external jars. They don't depend on other internal libraries. These libraries should be shared by functions (no need to have a library when it is used only by a function).</li>
-      <li>functions: everything else. It is harder to see a case of "direct" reuse of a function jar. Most times we'll only have code reuse. I would prefer to limit function to function dependencies.</li>
+      <li>API: They do not include implementation details, they do not have dependencies (or at most they have very common dependencies like mailet-api, javamail, commons-logging).</li>
+      <li>Library: They only depend on API modules or external jars. They don't depend on other internal libraries. These libraries should be shared by functions (no need to have a Library when it is used only by a function).</li>
+      <li>Functions: Everything else. It is harder to see a case of "direct" reuse of a function jar. Most times we'll only have code reuse. It is preferable to limit Function to Functions dependencies.</li>
     </ul>
     
   <section name="Server Coding Guidelines">

Modified: james/server/trunk/src/site/xdoc/feature-persistence.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-persistence.xml?rev=1090212&r1=1090211&r2=1090212&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-persistence.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-persistence.xml Fri Apr  8 11:43:04 2011
@@ -27,9 +27,9 @@
 
   <section name="Mailbox and Mailstore">
   
-    <p><b>Mailbox</b> is for users' Inbox, Sent Items, Trash... folders.</p>
+    <p><u><b>Mailbox</b> is for users' Inbox, Sent Items, Trash... folders</u>.</p>
       
-    <p><b>Mailstore</b> is for spam, error,... mails, so nothing to do with users visible mails.</p>
+    <p><u><b>Mailstore</b> is for spam, error,... mails, so nothing to do with users visible mails</u>.</p>
 
     <p>Both mailbox and mailstore use database connection defined via database.properties 
        in case of database access.</p>

Modified: james/server/trunk/src/site/xdoc/feature-security.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-security.xml?rev=1090212&r1=1090211&r2=1090212&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-security.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-security.xml Fri Apr  8 11:43:04 2011
@@ -27,13 +27,14 @@
 
   <section name="Protocol Security">
 
-    <p>TLS is supported.</p>
+    <p>Apache James Server support TLS (<a href="config-ssl-tls.html">read more</a>).</p>
 
   </section>
   
   <section name="User Credential Security">
 
-    <p>LDAP is supported.</p>
+    <p>Apache James Server supports partially LDAP  (<a href="config-users.html">read more</a>) - 
+       This is still a work in progress.</p>
 
   </section>
   

Modified: james/server/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/index.xml?rev=1090212&r1=1090211&r2=1090212&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/index.xml (original)
+++ james/server/trunk/src/site/xdoc/index.xml Fri Apr  8 11:43:04 2011
@@ -36,7 +36,7 @@
     <div id="tabs" style="min-width:550px;">
     
       <ul>
-        <li><a href="#tabs-1">James Server 3</a></li>
+        <li><a href="#tabs-1">Apache James Server 3</a></li>
         <li><a href="#tabs-2">Advantages</a></li>
       </ul>
 
@@ -46,29 +46,29 @@
 			<div class="ui-state-highlight ui-corner-all" style="margin-top: 20px; padding: 0 .7em;"> 
 				<p>
                   <span class="ui-icon ui-icon-info" style="float: left; margin-right: .3em;"></span>
-				  <strong>Hey!</strong> James Server 3.0-M3 is out - <a href="quick-start.html">Click here to Quick Start James!.</a>
+				  <span style="font-weight:bold; color:white;">Hey! Apache James Server 3.0-M3 is out - <a href="quick-start.html" style="color:white;">Click here to Quick Start Apache James Server!.</a>
                   Some issues are identified in some use cases with clients such as Outlook Express,...
-                  You are kindly invited to report any issue on <a href="https://issues.apache.org/jira/browse/JAMES">https://issues.apache.org/jira/browse/JAMES</a>
-                  or on our mailing list (<a href="http://james.apache.org/mail.html">http://james.apache.org/mail.html</a>)
+                  You are kindly invited to report any issue on <a href="https://issues.apache.org/jira/browse/JAMES" style="color:white;">https://issues.apache.org/jira/browse/JAMES</a>
+                  or on our mailing list (<a href="http://james.apache.org/mail.html" style="color:white;">http://james.apache.org/mail.html</a>)</span>
                 </p>
 			</div>
 		</div>
       
-	    <p>The Java Apache Mail Enterprise Server (a.k.a. Apache James) Version 3 
+	    <p>The Apache Java Mail Server Version 3.0
 	      is a 100% pure Java SMTP, IMAP4 and POP3 Mail 
 	      server designed to be a complete and portable enterprise mail engine solution.  
-	      James is based on currently available open protocols.</p>
+	      Apache James Server is based on currently available open protocols.</p>
 	    
-	    <p>This documentation is intended to be an introduction to the concepts behind the James usage, as well 
+	    <p>This documentation is intended to be an introduction to the concepts behind the Apache James Server usage, as well 
 	      as a guide to <a href="install.html">install</a>, <a href="config.html">configure</a> , 
 	      <a href="manage.html">manage</a>, <a href="monitor.html">monitor</a> 
-	      and <a href="dev.html">develop</a> James server.</p>
+	      and <a href="dev.html">develop</a> Apache James Server.</p>
 	      
-        <p>Download James Mail Server 3.0-M3 and <a href="quick-start.html">quick-start</a> it!</p>
+        <p>Download Apache James Mail Server 3.0-M3 and <a href="quick-start.html">quick-start</a> it!</p>
         <p>
           <span class="minibutton btn-download">
             <a href="javascript:window.location='http://james.apache.org/download.cgi#Apache_James_Server';">
-              <span><span class="icon"></span>Early James Server 3.0-M3</span>
+              <span><span class="icon"></span>Early Apache James Server 3.0-M3</span>
             </a>
           </span>
         </p>
@@ -76,19 +76,19 @@
         <p>
           <span class="minibutton btn-download">
             <a href="javascript:window.location='http://people.apache.org/builds/james/nightly/';">
-              <span><span class="icon"></span>Snapshot James Server 3.0</span>
+              <span><span class="icon"></span>Snapshot Apache James Server 3.0</span>
             </a>
           </span>
         </p>
 	
-        <p>James 3.0 represents the leading edge of development. This codestream has many more
+        <p>Apache James Server 3.0 represents the leading edge of development. This codestream has many more
           features than the 2.3 code, but is not as well tested in production. Reasonable
           configuration compatibility has been retained with 2.3.2.</p>
           
-        <p>James 3.0 requires Java 1.5 but Java 1.6 is recommended. A migration guide for 
+        <p>Apache James Server 3.0 requires Java 1.5 but Java 1.6 is recommended. A migration guide for 
            users willing to upgrade from 2.3 to 3.0 is <a href="upgrade-2.3.html">available</a>.</p>
            
-         <p>The NNTP News server and the mailing list manager present in James 2.3 have been 
+         <p>The NNTP News server and the Mailing List Manager present in Apache James Server 2.3 have been 
             temporary removed from the 3.0 release line.</p>
     
      </div>
@@ -106,12 +106,12 @@
 	           
 	        <p>Supports currently available IETF protocols, including SMTP, LMTP, POP3 and IMAP4.</p>
 	         
-	        <p>James is able to store user and message data either in a file-system (Maildir), 
+	        <p>Apache James Server is able to store user and message data either in a file-system (Maildir), 
 	           any JPA-compatible database and even JCR, allowing fast, reliable, 
 	           even real-time replicated storage.</p>
 	         
 	        <p>Provides a powerful, flexible mail application engine through support for the Apache Mailet 
-	           API.  With its Mailet pipeline architecture, James can be used not only to provide standard e-mail 
+	           API.  With its Mailet pipeline architecture, Apache James Server can be used not only to provide standard e-mail 
 	           services, but also to implement custom e-mail applications.</p>
 	           
 	      </subsection>
@@ -142,13 +142,13 @@
 
   	      <subsection name="Extensible">
 	    
-	        <p>James serves as a mail application platform.</p>
+	        <p>Apache James Server serves as a mail application platform.</p>
 	        
-	        <p>The James project hosts the Apache Mailet API, 
+	        <p>The Apache James Project hosts the Apache Mailet API, 
 	          and provides the Mailet container. These features makes it easy
 	          to design, write, and deploy custom applications for mail processing.</p>
 	          
-	        <p>This modularity and ease of customization is one of James' 
+	        <p>This modularity and ease of customization is one of Apache James' 
 	           strengths, and can allow administrators to produce powerful
                applications surprisingly easily. - <a href="dev-extend.html">read more</a></p>
 	 
@@ -160,10 +160,10 @@
         
  	      <subsection name="Developer-Friendly">
 	    
-	        <p>James 3.0 is now built on top of Spring 3.0 in replacement of trunk version of the <a href="http://avalon.apache.org/">Avalon</a> Application Framework.
+	        <p>Apache James Server 3.0 is now built on top of Spring 3.0 in replacement of trunk version of the <a href="http://avalon.apache.org/">Avalon</a> Application Framework.
 	           With Spring, We keep the good development practices introduced by Avalon such as 
 	           Component Oriented Programming and  Inversion of Control. The stable and robust 
-	           Spring container provides a strong foundation for the James server.</p>
+	           Spring container provides a strong foundation for the Apache James Server.</p>
 	    
 	        <p>The internal and exposed APIs for this 3.0-M3 release are under current validation and are 
 	          expected to be subject to change - <a href="dev.html">read more</a>.</p>
@@ -176,7 +176,7 @@
 	
           <subsection name="Performant">
            
-            <p>A special focuss has been brought to the performance: James can process more than
+            <p>A special focuss has been brought to the performance: Apache James Server can process more than
                100 mails per second. Deployed in production environments and has proven itself 
                to be a robust  and high performance mail solution. Tests indicate that 
                version 3.0 is able to maintain a constant mail throughput rate of thousands of 
@@ -192,7 +192,7 @@
         
           <subsection name="Secured">
         
-            <p>James is a secured mail server by default - <a href="feature-security.html">read more</a>.</p>
+            <p>Apache James Server is a secured mail server by default - <a href="feature-security.html">read more</a>.</p>
         
           </subsection>
 

Modified: james/server/trunk/src/site/xdoc/manage.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage.xml?rev=1090212&r1=1090211&r2=1090212&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage.xml (original)
+++ james/server/trunk/src/site/xdoc/manage.xml Fri Apr  8 11:43:04 2011
@@ -42,7 +42,7 @@
     <p>You can manage James via:</p>
     
     <ol>
-      <li><a href="#Manage_via_Cli">CLI (Client Line Interface)</a></li>
+      <li><a href="#Manage_via_CLI">CLI (Client Line Interface)</a></li>
       <li><a href="#Manage_via_JMX">JMX (Java Management Extension)</a></li>
     </ol>
     



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org