CVS: jcontainer/loom/site/xdocs/guide/assemblers creating-a-server-application.xml,1.3,1.4 index.xml,1.4,1.5 what-is-a-server-application.xml,1.3,1.4
Peter Donald <pdonald-yCVjj/[email protected]> Wed, 3 Dec 2003 04:45:24 -0600
| Newsgroups | gmane.comp.java.jcontainer.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/jcontainer/jcontainer/loom/site/xdocs/guide/assemblers
In directory hogshead.codehaus.org:/tmp/cvs-serv21491/site/xdocs/guide/assemblers
Modified Files:
creating-a-server-application.xml index.xml
what-is-a-server-application.xml
Log Message:
Styled codebase
Index: creating-a-server-application.xml
===================================================================
RCS file: /cvsroot/jcontainer/jcontainer/loom/site/xdocs/guide/assemblers/creating-a-server-application.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- creating-a-server-application.xml 31 Jul 2003 20:29:40 -0000 1.3
+++ creating-a-server-application.xml 3 Dec 2003 10:44:51 -0000 1.4
@@ -1,70 +1,72 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<document>
- <properties>
- <title>Guide - Creating a Server Application</title>
- <author email="peter at apache.org">Peter Donald</author>
- </properties>
- <body>
- <section name="Introduction">
- <p>
+ <properties>
+ <title>Guide - Creating a Server Application</title>
+ <author email="peter at apache.org">Peter Donald</author>
+ </properties>
+ <body>
+ <section name="Introduction">
+ <p>
This document will describe the process for assembling your first Server
Application. There is a number of steps in creating a Server Application.
These are;
- </p>
- <ol>
- <li>Select the blocks you wish to assemble.</li>
- <li>Write the config.xml file.</li>
- <li>Write the assembly.xml file.</li>
- <li>Write the environment.xml file.</li>
- <li>Package the component and related resources into a sar file.</li>
- </ol>
- </section>
- <section name="Select the Blocks to Assemble">
- <p>
+ </p>
+ <ol>
+ <li>Select the blocks you wish to assemble.</li>
+ <li>Write the config.xml file.</li>
+ <li>Write the assembly.xml file.</li>
+ <li>Write the environment.xml file.</li>
+ <li>Package the component and related resources into a sar file.</li>
+ </ol>
+ </section>
+ <section name="Select the Blocks to Assemble">
+ <p>
As a assembler it is your responsibility to select the particular Blocks
required to build your application. You may aquire the Blocks from a number
of sources depending on your resources. You may use the core Blocks supplied
with Loom, contract someone to build the component or download the Block
from an online repository.
- </p>
- </section>
- <section name="Write the config.xml file">
- <p>
+ </p>
+ </section>
+ <section name="Write the config.xml file">
+ <p>
Configuration data for blocks is stored in the config.xml file.
For more detail on the format of config.xml see the
- <a href="../../reference/config-xml-specification.html">specification</a>.
- </p>
- </section>
- <section name="Write the assembly.xml file">
- <p>
+ <a href="../../reference/config-xml-specification.html">specification</a>.
+ </p>
+ </section>
+ <section name="Write the assembly.xml file">
+ <p>
The next stage is to write the assembly.xml file. The assembly.xml specifies
the instances of Blocks that are part of the Server Application. Each
Block has a name. Each block may also have dependencies that need to be
satisfied and this can be done via the 'provide' sub-elements. The
provide element maps block instances from the Server Application namespace
to the Block role namespace specified in BlockInfo files. For more detail
- on the format of assembly.xml see the <a href="../../reference/assembly-xml-specification.html">
+ on the format of assembly.xml see the
+ <a href="../../reference/assembly-xml-specification.html">
specification</a>.
- </p>
- </section>
- <section name="Write the environment.xml file">
- <p>
+ </p>
+ </section>
+ <section name="Write the environment.xml file">
+ <p>
The next stage is to write the environment.xml file. The environment.xml is used to
configure the code-based security policy, log management and thread pooling.
For more detail on the format of environment.xml see the
- <a href="../../reference/environment-xml-specification.html">specification</a>.
- </p>
- </section>
- <section name="Create the sar file">
- <p>
+ <a href="../../reference/environment-xml-specification.html">specification</a>.
+ </p>
+ </section>
+ <section name="Create the sar file">
+ <p>
The sar file format is the standard distribution format of Loom Server
Applications. It is a standard Jar file with a specific directory layout.
The config.xml, environment.xml and assembly.xml file must be stored in
- <code>SAR-INF/</code> directory of the archive. All jar files, including
+ <code>SAR-INF/</code> directory of the archive. All jar files, including
both those that contain blocks and those that contain support classes
- should be stored in the <code>SAR-INF/lib/</code> directory.
- </p>
- </section>
+ should be stored in the
+ <code>SAR-INF/lib/</code> directory.
+ </p>
+ </section>
- </body>
+ </body>
</document>
Index: index.xml
===================================================================
RCS file: /cvsroot/jcontainer/jcontainer/loom/site/xdocs/guide/assemblers/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- index.xml 31 Jul 2003 20:29:40 -0000 1.4
+++ index.xml 3 Dec 2003 10:44:51 -0000 1.5
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<document>
<properties>
- <title>Guide - for Server Assemblers</title>
- <author email="jcontainer-interest-yCVjj/[email protected] ">Loom Documentation Team</author>
- </properties>
+ <title>Guide - for Server Assemblers</title>
+ <author email="jcontainer-interest-yCVjj/[email protected] ">Loom Documentation Team</author>
+ </properties>
<body>
<section name="Who Should Read This Guide?">
<p>
Index: what-is-a-server-application.xml
===================================================================
RCS file: /cvsroot/jcontainer/jcontainer/loom/site/xdocs/guide/assemblers/what-is-a-server-application.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- what-is-a-server-application.xml 31 Jul 2003 20:29:40 -0000 1.3
+++ what-is-a-server-application.xml 3 Dec 2003 10:44:51 -0000 1.4
@@ -1,27 +1,27 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<document>
- <properties>
- <title>Guide - What is a Server Application?</title>
- <author email="peter at apache.org">Peter Donald</author>
- <author email="[email protected]">Berin Loritsch</author>
- </properties>
- <body>
- <section name="Introduction">
- <p>
+ <properties>
+ <title>Guide - What is a Server Application?</title>
+ <author email="peter at apache.org">Peter Donald</author>
+ <author email="[email protected]">Berin Loritsch</author>
+ </properties>
+ <body>
+ <section name="Introduction">
+ <p>
In Loom, a Server Application is a set of Blocks that act in concert
to provide a unified user service. Example Server Applications include a Mail
Server, File Server, Web Server etc. The Server Application is a high level
component that contains a set of Block components.
- </p>
- <p>
+ </p>
+ <p>
A Server Application requires a number of components other than Blocks to
be complete. A Server Application requires configuration files to define
Server Application wide settings (threading, security, logging), to define
how blocks are wired together, and to define configuration data for the
Block instances. A Block can also require other resources that are
application specific.
- </p>
- </section>
+ </p>
+ </section>
- </body>
+ </body>
</document>