avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dona...@apache.org
Subject cvs commit: jakarta-avalon-cornerstone/src/xdocs/dtd changes-v10.dtd characters.ent document-v10.dtd
Date Sat, 22 Jun 2002 10:43:47 GMT
donaldp     2002/06/22 03:43:47

  Modified:    src/xdocs changes.xml index.xml
  Removed:     src/xdocs book.xml cornerstone.uris features.xml
                        to-merge.txt
               src/xdocs/dtd changes-v10.dtd characters.ent
                        document-v10.dtd
  Log:
  Update the documentation to Anakia style docs.
  
  Revision  Changes    Path
  1.5       +2 -9      jakarta-avalon-cornerstone/src/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-cornerstone/src/xdocs/changes.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- changes.xml	19 Nov 2001 12:27:27 -0000	1.4
  +++ changes.xml	22 Jun 2002 10:43:47 -0000	1.5
  @@ -1,13 +1,6 @@
  -<?xml version="1.0"?>
  -
  -<!DOCTYPE changes SYSTEM "dtd/changes-v10.dtd">
  +<?xml version="1.0" encoding="UTF-8"?>
   
   <changes title="Avalon History of Changes">
  -  <devs>
  -    <person name="Federico Barbieri" email="fede@apache.org" id="FB"/>
  -    <person name="Berin Loritsch" email="bloritsch@apache.org" id="BL"/>
  -    <person name="Peter Donald" email="peter@apache.org" id="PD"/>
  -  </devs>
   
   <release version="3.1a2" date="Unreleased">
       <action dev="BL" type="add">
  @@ -25,4 +18,4 @@
     </action>
   </release>
   
  -</changes>
  +</changes>
  \ No newline at end of file
  
  
  
  1.9       +127 -137  jakarta-avalon-cornerstone/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-cornerstone/src/xdocs/index.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- index.xml	29 May 2002 21:14:05 -0000	1.8
  +++ index.xml	22 Jun 2002 10:43:47 -0000	1.9
  @@ -1,141 +1,131 @@
   <?xml version="1.0"?>
   
  -<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
  -
   <document>
  -  <header>
  -    <title>Cornerstone - Overview</title>
  -    <authors>
  -      <person name="Avalon Documentation Team" email="avalon-dev@jakarta.apache.org"/>
  -    </authors>
  -  </header>
  -  <body>
  -    <s1 title="Introduction">
  -      <p>
  -        Cornerstone is a set of services for the Phoenix kernel. It contains "blocks"
  -        that plug into Phoenix. 
  -      </p>
  -    </s1>
  -    <s1 title="Service List (&amp; the blocks that implement them)">
  -      <s2 title="ConnectionManager">
  -        <p>
  -          The ConnectionManager service provides a facility to listen for incoming socket
connections.
  -        </p>
  -        <p>
  -          The DefaultConnectionManager block gives a thread pooled implementation of this
service.
  -          If there  were many server components all depending on this block, they would
all share 
  -          the same thread pool.
  -        </p>   
  -      </s2>
  -      <s2 title="DataSourceSelector">
  -        <p>
  -          The DataSourceSelector service provides a way to select DataSourceComponent.
  -        </p>
  -        <p>
  -          The DefaultDataSourceSelector block gives a set of ready to use DataSourceComponents.
  -        </p>   
  -      </s2>      
  -      <s2 title="DocumentBuilderFactory">
  -        <p>
  -          The DocumentBuilderFactory service provides a way to depend on a DOM Parser.
 This
  -          implements the same methods (bar the factory one) that 
  -          javax.xml.parsers.DocumentBuilderFactory does.
  -        </p>
  -        <p>
  -          The DOMBuilderFactory block will instantiate a javax.xml.parsers.DocumentBuilderFactory
  -          parser as named in its configuration.
  -        </p>   
  -        <p>
  -          <strong>Note -</strong> One might ask why the javax.xml.parsers.DocumentBuilderFactory
  -          is not just used to load a parser.  The reason is that the factory method in
that abstract
  -          class will register the first DOM parser loaded as the DOM parser to use for
the whole VM.
  -          Clearly for a multi-server solution like Phoenix we must allow differet servers
to load
  -          their preferred parser.  After all not all parser are created equal (in terms
of features,
  -          speed and size).
  -        </p>        
  -      </s2>
  -      <s2 title="PacketManager">
  -        <p>
  -          The PacketManager service provides a facility to listen for incoming datagram
connections.
  -        </p>
  -        <p>
  -          The DefaultPacketManager block gives a thread pooled implementation of this service.
  -          If there  were many server components all depending on this block, they would
all share 
  -          the same thread pool.
  -        </p>    
  -      </s2>            
  -      <s2 title="SAXParserFactory">
  -        <p>
  -          The SAXParserFactory service provides a way to depend on a SAX Parser.  This
implements
  -          the same methods (bar the factory one) that javax.xml.parsers.SAXParserFactory
does.
  -        </p>
  -        <p>
  -          The SAXParserFactoryImpl block will instantiate a javax.xml.parsers.SAXParserFactory
  -          parser as named in its configuration.
  -        </p>   
  -        <p>
  -          <strong>Note -</strong> Same note as for DocumentBuilderFactory above.
  -        </p>        
  -      </s2>
  -      <s2 title="TimeScheduler">
  -        <p>
  -          The TimeScheduler service provides a way to a depending block to do things an
certain intervals.
  -        </p>
  -        <p>
  -          The DefaultTimeScheduler block implements the service.
  -        </p>   
  -        <p>
  -          Used in conjunction with the service is a TimeTrigger.  There are two such tiggers
at the
  -          moment - CronTimeTrigger and PeriodicTimeTigger.
  -        </p>        
  -      </s2>      
  -      <s2 title="SOAPification">
  -        <p>
  -          The SOAPification service provides a way to publish an arbitart interface remotely
using SOAP.
  -        </p>
  -        <p>
  -          The Glue block implements this service using the 'Glue' from 'The Mind Electric'.
 As this
  -          product is commercial, we 1) do not include the jar for it in the source distro,
2) do not make
  -          available for download a Cornerstone that includes the Glue block.
  -        </p>   
  -        <p>
  -          There is some question currentl as to whether Glue 2,x works with with Pheonix.
 Glue 1.3 does.
  -        </p>        
  -      </s2>     
  -      <s2 title="SocketManager">
  -        <p>
  -          The SocketManager service provides a way to lookup a factory for server of client
sockets.
  -        </p>
  -        <p>
  -          The DefaultSocketManager block implements this service
  -        </p>
  -      </s2>
  -      <s2 title="Store">
  -        <p>
  -          The Store service provides a way to store named Objects or Streams without knowing
how they
  -          are stored.
  -        </p>
  -        <p>
  -          The RepositoryManager block implements this service and provides (in invocation
of select(..) ) an 
  -          appropriate Respository.  The two configurable implementations use the local
file system for 
  -          storage.
  -        </p>
  -      </s2>
  -      <s2 title="ThreadManager">
  -        <p>
  -          The ThreadManager service provides a way get default or named Thread Pool.
  -        </p>
  -        <p>
  -          The DefaultThreadManager block implements this service an leans on Excalibur

  -          implementations of ThreadPool.
  -        </p>   
  -      </s2>      
  -    </s1>   
  -  </body>  
  -  <footer>
  -    <legal>
  -      Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
  -      $Revision$ $Date$
  -    </legal>
  -  </footer>
  +    <properties>
  +        <title>Cornerstone - Overview</title>
  +        <author email="avalon-dev@jakarta.apache.org">Avalon Documentation Team</author>
  +    </properties>
  +    <body>
  +        <section name="Introduction">
  +            <p>
  +              Cornerstone is a set of services for the Phoenix kernel. It contains "blocks"
  +              that plug into Phoenix.
  +            </p>
  +        </section>
  +        <section name="Service List (and the blocks that implement them)">
  +            <subsection name="ConnectionManager">
  +                <p>
  +                  The ConnectionManager service provides a facility to listen for incoming
socket connections.
  +                </p>
  +                <p>
  +                  The DefaultConnectionManager block gives a thread pooled implementation
of this service.
  +                  If there  were many server components all depending on this block, they
would all share
  +                  the same thread pool.
  +                </p>
  +            </subsection>
  +            <subsection name="DataSourceSelector">
  +              <p>
  +                The DataSourceSelector service provides a way to select DataSourceComponent.
  +              </p>
  +              <p>
  +                The DefaultDataSourceSelector block gives a set of ready to use DataSourceComponents.
  +              </p>
  +            </subsection>
  +            <subsection name="DocumentBuilderFactory">
  +              <p>
  +                The DocumentBuilderFactory service provides a way to depend on a DOM Parser.
 This
  +                implements the same methods (bar the factory one) that
  +                javax.xml.parsers.DocumentBuilderFactory does.
  +              </p>
  +              <p>
  +                The DOMBuilderFactory block will instantiate a javax.xml.parsers.DocumentBuilderFactory
  +                parser as named in its configuration.
  +              </p>
  +              <p>
  +                <strong>Note -</strong> One might ask why the javax.xml.parsers.DocumentBuilderFactory
  +                is not just used to load a parser.  The reason is that the factory method
in that abstract
  +                class will register the first DOM parser loaded as the DOM parser to use
for the whole VM.
  +                Clearly for a multi-server solution like Phoenix we must allow differet
servers to load
  +                their preferred parser.  After all not all parser are created equal (in
terms of features,
  +                speed and size).
  +              </p>
  +            </subsection>
  +            <subsection name="PacketManager">
  +              <p>
  +                The PacketManager service provides a facility to listen for incoming datagram
connections.
  +              </p>
  +              <p>
  +                The DefaultPacketManager block gives a thread pooled implementation of
this service.
  +                If there  were many server components all depending on this block, they
would all share
  +                the same thread pool.
  +              </p>
  +            </subsection>
  +            <subsection name="SAXParserFactory">
  +              <p>
  +                The SAXParserFactory service provides a way to depend on a SAX Parser.
 This implements
  +                the same methods (bar the factory one) that javax.xml.parsers.SAXParserFactory
does.
  +              </p>
  +              <p>
  +                The SAXParserFactoryImpl block will instantiate a javax.xml.parsers.SAXParserFactory
  +                parser as named in its configuration.
  +              </p>
  +              <p>
  +                <strong>Note -</strong> Same note as for DocumentBuilderFactory
above.
  +              </p>
  +            </subsection>
  +            <subsection name="TimeScheduler">
  +              <p>
  +                The TimeScheduler service provides a way to a depending block to do things
an certain intervals.
  +              </p>
  +              <p>
  +                The DefaultTimeScheduler block implements the service.
  +              </p>
  +              <p>
  +                Used in conjunction with the service is a TimeTrigger.  There are two such
tiggers at the
  +                moment - CronTimeTrigger and PeriodicTimeTigger.
  +              </p>
  +            </subsection>
  +            <subsection name="SOAPification">
  +              <p>
  +                The SOAPification service provides a way to publish an arbitart interface
remotely using SOAP.
  +              </p>
  +              <p>
  +                The Glue block implements this service using the 'Glue' from 'The Mind
Electric'.  As this
  +                product is commercial, we 1) do not include the jar for it in the source
distro, 2) do not make
  +                available for download a Cornerstone that includes the Glue block.
  +              </p>
  +              <p>
  +                There is some question currentl as to whether Glue 2,x works with with
Pheonix.  Glue 1.3 does.
  +              </p>
  +            </subsection>
  +            <subsection name="SocketManager">
  +              <p>
  +                The SocketManager service provides a way to lookup a factory for server
of client sockets.
  +              </p>
  +              <p>
  +                The DefaultSocketManager block implements this service
  +              </p>
  +            </subsection>
  +            <subsection name="Store">
  +              <p>
  +                The Store service provides a way to store named Objects or Streams without
knowing how they
  +                are stored.
  +              </p>
  +              <p>
  +                The RepositoryManager block implements this service and provides (in invocation
of select(..) ) an
  +                appropriate Respository.  The two configurable implementations use the
local file system for
  +                storage.
  +              </p>
  +            </subsection>
  +            <subsection name="ThreadManager">
  +              <p>
  +                The ThreadManager service provides a way get default or named Thread Pool.
  +              </p>
  +              <p>
  +                The DefaultThreadManager block implements this service an leans on Excalibur
  +                implementations of ThreadPool.
  +              </p>
  +            </subsection>
  +        </section>
  +    </body>
   </document>
  
  
  

--
To unsubscribe, e-mail:   <mailto:avalon-cvs-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@jakarta.apache.org>


Mime
View raw message