Return-Path: Delivered-To: apmail-jakarta-avalon-cvs-archive@apache.org Received: (qmail 26187 invoked from network); 23 May 2002 10:36:58 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 May 2002 10:36:58 -0000 Received: (qmail 6708 invoked by uid 97); 23 May 2002 10:36:58 -0000 Delivered-To: qmlist-jakarta-archive-avalon-cvs@jakarta.apache.org Received: (qmail 6692 invoked by uid 97); 23 May 2002 10:36:58 -0000 Mailing-List: contact avalon-cvs-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon CVS List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-cvs@jakarta.apache.org Received: (qmail 6671 invoked by uid 97); 23 May 2002 10:36:57 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: 23 May 2002 10:36:54 -0000 Message-ID: <20020523103654.26944.qmail@icarus.apache.org> From: donaldp@apache.org To: jakarta-avalon-phoenix-cvs@apache.org Subject: cvs commit: jakarta-avalon-phoenix/src/xdocs/stylesheets project.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 @@ - -
Features - - - +
-
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 @@
A future - - - +
@@ -22,12 +20,20 @@

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

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

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 @@
- Getting Started - + Getting Started -
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 @@ -
- Guide - for Administrators - - - -
- -
-

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

- -

- This documentation will describe the care and feeding of the Avalon - Phoenix kernel from the point of view of the administrator. -

- - -

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

- -
- +
+ Guide - for Administrators + +
+ +
+

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

+ +

+ This documentation will describe the care and feeding of the Avalon + Phoenix kernel from the point of view of the administrator. +

+ + +

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

+ +
+ 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 @@ -
- Guide - Architectural overview - -
- -
-

- This document briefly describes the Phoenix server architecture. -

-
-
-

- Phoenix hosts one or more server applications at the same time in the same Virtual machine. -

-
Phoenix layer diagram
-
-

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

-
-
-

- Phoenix application are distriuted in a single archive. -

- -

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

-
Phoenix application in block view
-
- - -

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

-
- Phoenix application in block jar view -
-
- - -

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

-
FtpServer, a real Phoenix application
-
- -

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

-
- +
+ Guide - Architectural overview + +
+ +
+

+ This document briefly describes the Phoenix server architecture. +

+
+
+

+ Phoenix hosts one or more server applications at the same time in the same Virtual machine. +

+
+ Phoenix layer diagram +
+
+ +
+

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

+
+
+

+ Phoenix application are distriuted in a single archive. +

+ +

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

+
+ Phoenix application in block view +
+
+ +
+ + +

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

+
+ Phoenix application in block jar view +
+ +
+
+ + +

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

+
+ FtpServer, a real Phoenix application +
+
+ +
+ +

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

+
+ 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 @@
Guide - for Deployers - - - +
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 @@

The assembler takes pre-written blocks and glues these together to create a server application. Assemblers usually work closely with block developers.

-

Assembler Guide

+

Assembler Guide

The block developer creates reusable components (called blocks) that can be wired together to form a server applications.

-

Block Developers Guide

+

Block Developers Guide

 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 @@
  • Development roles
  • Administrator Guide
  • Application Deployer Guide
    • -
  • Server Application Assembler Guide
    • -
  • Block Developer Guide
    • +
  • Server Application Assembler Guide
    • +
  • Block Developer Guide
  • Example Configuration.
    • 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 @@ - - + + - - - - + + + + -- To unsubscribe, e-mail: For additional commands, e-mail: