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-phoenix/src/xdocs/stylesheets project.xml
Date Thu, 23 May 2002 10:36:54 GMT
donaldp     02/05/23 03:36:54

  Modified:    src/xdocs Tag: ANAKIA_DOCS features.xml
                        for-developers-a-future.xml getting-started.xml
                        guide-administrator.xml guide-architecture.xml
                        guide-deployers.xml guide-roles.xml index.xml
               src/xdocs/stylesheets Tag: ANAKIA_DOCS project.xml
  Added:       src/xdocs/assemblers Tag: ANAKIA_DOCS
                        assembly-xml-specification.xml
                        config-xml-specification.xml
                        creating-a-server-application.xml
                        environment-xml-specification.xml index.xml
                        what-is-a-server-application.xml
               src/xdocs/bdg Tag: ANAKIA_DOCS blockinfo-specification.xml
                        creating-a-block.xml index.xml
                        making-phoenix-compatible-comps.xml
                        what-is-a-block-listener.xml what-is-a-block.xml
                        what-is-an-application-listener.xml
  Removed:     src/xdocs Tag: ANAKIA_DOCS
                        guide-assemblers-creating-a-server-application.xml
                        guide-assemblers-what-is-a-server-application.xml
                        guide-assemblers.xml
                        guide-block-developers-creating-a-block.xml
                        guide-block-developers-making-phoenix-compatible-comps.xml
                        guide-block-developers-what-is-a-block-listener.xml
                        guide-block-developers-what-is-a-block.xml
                        guide-block-developers-what-is-an-application-listener.xml
                        guide-block-developers.xml
                        reference-assembly-xml-specification.xml
                        reference-blockinfo-specification.xml
                        reference-config-xml-specification.xml
                        reference-environment-xml-specification.xml
  Log:
  Move assemblers/block developers guide stuff into own sub directorys
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.5.2.2   +1 -6      jakarta-avalon-phoenix/src/xdocs/features.xml
  
  Index: features.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/features.xml,v
  retrieving revision 1.5.2.1
  retrieving revision 1.5.2.2
  diff -u -r1.5.2.1 -r1.5.2.2
  --- features.xml	21 May 2002 11:58:19 -0000	1.5.2.1
  +++ features.xml	23 May 2002 10:36:53 -0000	1.5.2.2
  @@ -1,14 +1,9 @@
   <?xml version="1.0"?>
  -
   <document>
  -
    <header>
     <title>Features</title>
  -
  -    <author name="Leo Simons" email="leosimons@apache.org"/>
  -
  +  <author name="Leo Simons" email="leosimons@apache.org"/>
    </header>
  -
   <body>
   
   <section name="Introduction">
  
  
  
  1.1.2.2   +11 -5     jakarta-avalon-phoenix/src/xdocs/for-developers-a-future.xml
  
  Index: for-developers-a-future.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/for-developers-a-future.xml,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- for-developers-a-future.xml	21 May 2002 11:58:19 -0000	1.1.2.1
  +++ for-developers-a-future.xml	23 May 2002 10:36:53 -0000	1.1.2.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>A future</title>
  -
  -      <author name="Paul Hammant" email="Paul_Hammant@yahoo.com"/>
  -
  +    <author name="Paul Hammant" email="Paul_Hammant@yahoo.com"/>
     </header>
     <body>
       <section name="Introduction">
  @@ -22,12 +20,20 @@
           <graphic srccredit="&#169; Sun Microsystems" fileref="http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg"
format="JPEG"/>
         </figure>
         <p>
  -        If that rackable server had 32 such CPUs, each with 128Mb of memory all booting
Phoenix. And if the CPUs shared a single hard drive, we might have a machine that was tuned
to CPU intensive activities. Cocoon/Tomcat, EJB clusters, might be load balanced by one of
the CPUs running a Phoenix load balancer.  Alternate scenarios are for virtual site hosting.
 It could be a "1U" render or bean farm with each internal CPU having its own TCP/IP address.
  +        If that rackable server had 32 such CPUs, each with 128Mb of memory all
  +        booting Phoenix. And if the CPUs shared a single hard drive, we might have
  +        a machine that was tuned to CPU intensive activities. Cocoon/Tomcat, EJB
  +        clusters, might be load balanced by one of the CPUs running a Phoenix load
  +        balancer.  Alternate scenarios are for virtual site hosting.  It could be
  +        a "1U" render or bean farm with each internal CPU having its own TCP/IP
  +        address.
         </p>
       </section>
       <section name="Is all this possible?">
         <p>
  -        Well there are already romable J2SE implementations that are available for StrongARM
chips on Compaq's handheld iPAQ.  We are there already, but for the client side rather than
the server side.
  +        Well there are already romable J2SE implementations that are available for
  +        StrongARM chips on Compaq's handheld iPAQ.  We are there already, but for
  +        the client side rather than the server side.
         </p>
       </section>
     </body>
  
  
  
  1.4.2.3   +1 -3      jakarta-avalon-phoenix/src/xdocs/getting-started.xml
  
  Index: getting-started.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/getting-started.xml,v
  retrieving revision 1.4.2.2
  retrieving revision 1.4.2.3
  diff -u -r1.4.2.2 -r1.4.2.3
  --- getting-started.xml	22 May 2002 13:29:05 -0000	1.4.2.2
  +++ getting-started.xml	23 May 2002 10:36:53 -0000	1.4.2.3
  @@ -3,12 +3,10 @@
   <document>
   
    <header>
  -  <title>Getting Started</title>
  -
  +   <title>Getting Started</title>
      <author name="Avalon Documentation Team" email="avalon-dev@jakarta.apache.org"/>
      <author name="Leo Simons" email="email@leosimons.com"/>
      <author name="Paul Hammant" email="Paul_Hammant@yahoo.com"/>
  -
    </header>
   
   <body>
  
  
  
  1.1.2.4   +27 -30    jakarta-avalon-phoenix/src/xdocs/guide-administrator.xml
  
  Index: guide-administrator.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-administrator.xml,v
  retrieving revision 1.1.2.3
  retrieving revision 1.1.2.4
  diff -u -r1.1.2.3 -r1.1.2.4
  --- guide-administrator.xml	21 May 2002 12:18:32 -0000	1.1.2.3
  +++ guide-administrator.xml	23 May 2002 10:36:53 -0000	1.1.2.4
  @@ -1,34 +1,31 @@
   <?xml version="1.0"?>
   
   <document>
  -  <header>
  -    <title>Guide - for Administrators</title>
  -
  -      <author name="Berin Loritsch" email="bloritsch@apache.org"/>
  -
  -  </header>
  -  <body>
  -    <section name="Introduction">
  -      <p>
  -        Avalon is a Server Framework that provides or will provide for
  -        central administration, server pooling, and quicker time to market.
  -        The framework defines a standard method of piecing together server
  -        components and creating a server.
  -      </p>
  -      <subsection name="Target Audience">
  -        <p>
  -          This documentation will describe the care and feeding of the Avalon
  -          Phoenix kernel from the point of view of the administrator.
  -        </p>
  -      </subsection>
  -      <subsection name="Guide non-existent, but features are there">
  -	<p>
  -          We currently have no info on this whatsoever. However, this doesn't
  -	  mean that Phoenix is not easy to administrate - the contrary is true,
  -	  since our tight integration with JMX exposes the entire kernel at
  -	  runtime.
  -        </p>
  -      </subsection>
  -    </section>
  -  </body>
  +    <header>
  +        <title>Guide - for Administrators</title>
  +        <author name="Berin Loritsch" email="bloritsch@apache.org"/>
  +    </header>
  +    <body>
  +        <section name="Introduction">
  +            <p>
  +              Avalon is a Server Framework that provides or will provide for
  +              central administration, server pooling, and quicker time to market.
  +              The framework defines a standard method of piecing together server
  +              components and creating a server.
  +            </p>
  +            <subsection name="Target Audience">
  +                <p>
  +                  This documentation will describe the care and feeding of the Avalon
  +                  Phoenix kernel from the point of view of the administrator.
  +                </p>
  +            </subsection>
  +            <subsection name="Guide non-existent, but features are there">
  +                <p>We currently have no info on this whatsoever. However, this doesn't
  +               mean that Phoenix is not easy to administrate - the contrary is true,
  +               since our tight integration with JMX exposes the entire kernel at
  +               runtime.
  +                    </p>
  +            </subsection>
  +        </section>
  +    </body>
   </document>
  
  
  
  1.1.2.5   +81 -67    jakarta-avalon-phoenix/src/xdocs/guide-architecture.xml
  
  Index: guide-architecture.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-architecture.xml,v
  retrieving revision 1.1.2.4
  retrieving revision 1.1.2.5
  diff -u -r1.1.2.4 -r1.1.2.5
  --- guide-architecture.xml	22 May 2002 14:03:11 -0000	1.1.2.4
  +++ guide-architecture.xml	23 May 2002 10:36:53 -0000	1.1.2.5
  @@ -1,71 +1,85 @@
   <?xml version="1.0"?>
   
   <document>
  -  <header>
  -    <title>Guide - Architectural overview</title>
  -    <author name="Leo Simons" email="leosimons@apache.org"/>
  -  </header>
  -  <body>
  -    <section name="Introduction">
  -      <p>
  -        This document briefly describes the Phoenix server architecture.
  -      </p>
  -    </section>
  -    <section name="Multiple Server Application hosting">
  -      <p>
  -        Phoenix hosts one or more server applications at the same time in the same Virtual
machine.
  -      </p>
  -        <center><b>Phoenix layer diagram</b></center>
  -        <center><img src="./images/phoenix-layers.jpg"/></center>
  -      <p>
  -        Shown above are three hosted server applications.  A mail server that would implement
  -        multiple listeners for incoming and outgoing services (POP3, SMTP, IMAP etc). 
Outlook,
  -        Eudora and other mail clients would be able to connect to the server.  As it happens,
  -        Apache has a project in progress called "James" that provides these services and
Newsgroups.
  -        Also shown is a Web server.  That would respond to HTTP/HTTPS requests from similar
standards
  -        based clients and be able to host it's own applications (web-apps and virtual websites).
Lastly,
  -        and non-existant currently at Apache is an EJB Server.  This would be able to host
it's own
  -        bean applications and might use the web server for it's HTTP needs.
  -      </p>
  -    </section>
  -    <section name="Packaging of a Server Application">
  -      <p>
  -        Phoenix application are distriuted in a single archive.
  -      </p>
  -      <subsection name="Packaging in terms of blocks">
  -        <p>
  -          Phoenix hosts server applications made up of blocks.  The blocks may depend on
libraries
  -          to function correctly.  The blocks are tied together with Assembly instructions
and Configured
  -          externally.
  -        </p>
  -          <center><b>Phoenix application in block view</b></center>
  -          <center><img src="./images/phoenix-app-block.jpg"/></center>
  -      </subsection>
  -      <subsection name="Packaging in terms of block jar files">
  -        <p>
  -          The server application is entirely contained withing one "sar" file.  Sar is
"Server ARchive".
  -          Each block is a jar file.  The dependant libraries are regular jars (placed
  -          within a directory "lib" insde the sar file).  The Assembly and configuration
instructions
  -          are in xml form and contained within a "conf" directory inside the sar file.
  -        </p>
  -        <figure>
  -          <title>Phoenix application in block jar view</title>
  -          <center><img src="./images/phoenix-app-blockjars.jpg"/></center>
  -        </figure>
  -      </subsection>
  -      <subsection name="FtpServer as a Phoenix application">
  -      <p>
  -        FtpServer (part of the Avalon/Cornerstone project) is distributed in sar form.
 Here is a
  -        view of it's blocks.  It has no third party jars that it depends on.
  -      </p>
  -          <center><b>FtpServer, a real Phoenix application</b></center>
  -          <center><img src="./images/phoenix-app-ftpserver.jpg"/></center>
  -      </subsection>
  -      <p>
  -        Notes - Phoenix does not limit the number of blocks that it allows in a sar file.
 We have taksdefs for Apache's Ant
  -        tool for making sar files.  See the "Block Developers Guide" (left
  -        margin of this page) for more what/how/why.
  -      </p>
  -    </section>
  -  </body>
  +    <header>
  +        <title>Guide - Architectural overview</title>
  +        <author name="Leo Simons" email="leosimons@apache.org"/>
  +    </header>
  +    <body>
  +        <section name="Introduction">
  +            <p>
  +              This document briefly describes the Phoenix server architecture.
  +            </p>
  +        </section>
  +        <section name="Multiple Server Application hosting">
  +            <p>
  +              Phoenix hosts one or more server applications at the same time in the same
Virtual machine.
  +            </p>
  +            <center>
  +                <b>Phoenix layer diagram</b>
  +            </center>
  +            <center>
  +                <img src="./images/phoenix-layers.jpg"/>
  +            </center>
  +            <p>
  +              Shown above are three hosted server applications.  A mail server that would
implement
  +              multiple listeners for incoming and outgoing services (POP3, SMTP, IMAP etc).
 Outlook,
  +              Eudora and other mail clients would be able to connect to the server.  As
it happens,
  +              Apache has a project in progress called "James" that provides these services
and Newsgroups.
  +              Also shown is a Web server.  That would respond to HTTP/HTTPS requests from
similar standards
  +              based clients and be able to host it's own applications (web-apps and virtual
websites). Lastly,
  +              and non-existant currently at Apache is an EJB Server.  This would be able
to host it's own
  +              bean applications and might use the web server for it's HTTP needs.
  +            </p>
  +        </section>
  +        <section name="Packaging of a Server Application">
  +            <p>
  +              Phoenix application are distriuted in a single archive.
  +            </p>
  +            <subsection name="Packaging in terms of blocks">
  +                <p>
  +                  Phoenix hosts server applications made up of blocks.  The blocks may
depend on libraries
  +                  to function correctly.  The blocks are tied together with Assembly instructions
and Configured
  +                  externally.
  +                </p>
  +                <center>
  +                    <b>Phoenix application in block view</b>
  +                </center>
  +                <center>
  +                    <img src="./images/phoenix-app-block.jpg"/>
  +                </center>
  +            </subsection>
  +            <subsection name="Packaging in terms of block jar files">
  +                <p>
  +                  The server application is entirely contained withing one "sar" file.
 Sar is "Server ARchive".
  +                  Each block is a jar file.  The dependant libraries are regular jars (placed
  +                  within a directory "lib" insde the sar file).  The Assembly and configuration
instructions
  +                  are in xml form and contained within a "conf" directory inside the sar
file.
  +                </p>
  +                <figure>
  +                    <title>Phoenix application in block jar view</title>
  +                    <center>
  +                        <img src="./images/phoenix-app-blockjars.jpg"/>
  +                    </center>
  +                </figure>
  +            </subsection>
  +            <subsection name="FtpServer as a Phoenix application">
  +                <p>
  +                  FtpServer (part of the Avalon/Cornerstone project) is distributed in
sar form.  Here is a
  +                  view of it's blocks.  It has no third party jars that it depends on.
  +                </p>
  +                <center>
  +                    <b>FtpServer, a real Phoenix application</b>
  +                </center>
  +                <center>
  +                    <img src="./images/phoenix-app-ftpserver.jpg"/>
  +                </center>
  +            </subsection>
  +            <p>
  +              Notes - Phoenix does not limit the number of blocks that it allows in a sar
file.  We have taksdefs for Apache's Ant
  +              tool for making sar files.  See the "Block Developers Guide" (left
  +              margin of this page) for more what/how/why.
  +            </p>
  +        </section>
  +    </body>
   </document>
  
  
  
  1.1.2.4   +1 -3      jakarta-avalon-phoenix/src/xdocs/guide-deployers.xml
  
  Index: guide-deployers.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-deployers.xml,v
  retrieving revision 1.1.2.3
  retrieving revision 1.1.2.4
  diff -u -r1.1.2.3 -r1.1.2.4
  --- guide-deployers.xml	21 May 2002 12:18:32 -0000	1.1.2.3
  +++ guide-deployers.xml	23 May 2002 10:36:53 -0000	1.1.2.4
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Guide - for Deployers</title>
  -
  -      <author name="Peter Donald" email="peter@apache.org"/>
  -
  +    <author name="Peter Donald" email="peter@apache.org"/>
     </header>
     <body>
       <section name="Introduction">
  
  
  
  1.1.2.2   +2 -2      jakarta-avalon-phoenix/src/xdocs/guide-roles.xml
  
  Index: guide-roles.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-roles.xml,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- guide-roles.xml	21 May 2002 11:58:19 -0000	1.1.2.1
  +++ guide-roles.xml	23 May 2002 10:36:53 -0000	1.1.2.2
  @@ -36,13 +36,13 @@
         <p>The assembler takes pre-written blocks and glues these together to create
a
          server application. Assemblers usually work closely with block developers.</p>
   
  -      <p><a href="guide-assemblers.html">Assembler Guide</a></p>
  +      <p><a href="assemblers/index.html">Assembler Guide</a></p>
       </section>
       <section name="The Block Developer">
         <p>The block developer creates reusable components (called blocks) that can
be
          wired together to form a server applications.</p>
   
  -      <p><a href="guide-block-developers.html">Block Developers Guide</a></p>
  +      <p><a href="bdg/index.html">Block Developers Guide</a></p>
       </section>
     </body>
   </document>
  
  
  
  1.7.2.4   +2 -2      jakarta-avalon-phoenix/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/index.xml,v
  retrieving revision 1.7.2.3
  retrieving revision 1.7.2.4
  diff -u -r1.7.2.3 -r1.7.2.4
  --- index.xml	21 May 2002 12:18:32 -0000	1.7.2.3
  +++ index.xml	23 May 2002 10:36:53 -0000	1.7.2.4
  @@ -52,8 +52,8 @@
               <li><a href="guide-roles.html">Development roles</a></li>
               <li><a href="guide-administrators.html">Administrator Guide</a></li>
               <li><a href="guide-deployers.html">Application Deployer Guide</a></li>
  -            <li><a href="guide-assembler.html">Server Application Assembler
Guide</a></li>
  -            <li><a href="guide-block-developers.html">Block Developer Guide</a></li>
  +            <li><a href="assemblers/index.html">Server Application Assembler
Guide</a></li>
  +            <li><a href="bdg/index.html">Block Developer Guide</a></li>
               <li><a href="guide-example-configuration.html">Example Configuration.</a></li>
             </ol>
           </subsection>
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.1   +54 -0     jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/assembly-xml-specification.xml
  
  
  
  
  1.1.2.1   +43 -0     jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/config-xml-specification.xml
  
  
  
  
  1.1.2.1   +80 -0     jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/creating-a-server-application.xml
  
  
  
  
  1.1.2.1   +115 -0    jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/environment-xml-specification.xml
  
  
  
  
  1.1.2.1   +47 -0     jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/index.xml
  
  
  
  
  1.1.2.1   +37 -0     jakarta-avalon-phoenix/src/xdocs/assemblers/Attic/what-is-a-server-application.xml
  
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.1   +93 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/blockinfo-specification.xml
  
  
  
  
  1.1.2.1   +73 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/creating-a-block.xml
  
  
  
  
  1.1.2.1   +48 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/index.xml
  
  
  
  
  1.1.2.1   +209 -0    jakarta-avalon-phoenix/src/xdocs/bdg/Attic/making-phoenix-compatible-comps.xml
  
  
  
  
  1.1.2.1   +68 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/what-is-a-block-listener.xml
  
  
  
  
  1.1.2.1   +47 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/what-is-a-block.xml
  
  
  
  
  1.1.2.1   +51 -0     jakarta-avalon-phoenix/src/xdocs/bdg/Attic/what-is-an-application-listener.xml
  
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.4   +6 -6      jakarta-avalon-phoenix/src/xdocs/stylesheets/Attic/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/stylesheets/Attic/project.xml,v
  retrieving revision 1.1.2.3
  retrieving revision 1.1.2.4
  diff -u -r1.1.2.3 -r1.1.2.4
  --- project.xml	22 May 2002 13:27:06 -0000	1.1.2.3
  +++ project.xml	23 May 2002 10:36:54 -0000	1.1.2.4
  @@ -21,17 +21,17 @@
               <item name="Development Roles" href="/guide-roles.html"/>
               <item name="for Administrators" href="/guide-administrator.html"/>
               <item name="for Deployers" href="/guide-deployers.html"/>
  -            <item name="for Assemblers" href="/guide-assemblers.html"/>
  -            <item name="for Block Developers" href="/guide-block-developers.html" />
  +            <item name="for Assemblers" href="/assemblers/index.html"/>
  +            <item name="for Block Developers" href="/bdg/index.html" />
               <item name="Example configuration" href="/guide-example-configuration.html"
/>
           </menu>
   
           <menu name="Reference">
               <item name="API Docs" href="/api/index.html"/>
  -            <item name="config.xml Specification" href="/reference-config-xml-specification.html"/>
  -            <item name="assembly.xml Specification" href="/reference-assembly-xml-specification.html"/>
  -            <item name="environment.xml Specification" href="/reference-environment-xml-specification.html"/>
  -            <item name="BlockInfo Specification" href="/reference-blockinfo-specification.html"
/>
  +            <item name="config.xml Specification" href="/assemblers/config-xml-specification.html"/>
  +            <item name="assembly.xml Specification" href="/assemblers/assembly-xml-specification.html"/>
  +            <item name="environment.xml Specification" href="/assemblers/environment-xml-specification.html"/>
  +            <item name="BlockInfo Specification" href="/bdg/blockinfo-specification.html"
/>
           </menu>
   
           <menu name="For Developers">
  
  
  

--
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