hammant 2003/03/23 15:43:54
Modified: src/xdocs Tag: RELEASE_402-branch features.xml
for-developers-a-future.xml
for-developers-alternate-kernel.xml
getting-started.xml
src/xdocs/mx Tag: RELEASE_402-branch xdoctags.xml
src/xdocs/stylesheets Tag: RELEASE_402-branch project.xml
Log:
some doc patches, reapplied from head
Revision Changes Path
No revision
No revision
1.9.2.1 +5 -5 avalon-phoenix/src/xdocs/Attic/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/xdocs/Attic/features.xml,v
retrieving revision 1.9
retrieving revision 1.9.2.1
diff -u -r1.9 -r1.9.2.1
--- features.xml 2 Aug 2002 15:16:33 -0000 1.9
+++ features.xml 23 Mar 2003 23:43:54 -0000 1.9.2.1
@@ -21,7 +21,7 @@
</ul>
</section>
-<section name="Flexible environment">
+<section name="Flexible Environment">
<p>Phoenix has native support for use in the following environments:</p>
<ul>
<li>command-line stand-alone program</li>
@@ -30,12 +30,12 @@
</ul>
</section>
-<section name="Integrated management">
+<section name="Integrated Management">
<p>Phoenix enables JMX management of your software:</p>
<ul>
- <li>All aspects of phoenix itself are manageable, including
+ <li>All aspects of Phoenix itself are manageable, including
startup/shutdown, deployment, management and logging.</li>
- <li>Applications running in phoenix are manageable, exposing
+ <li>Applications running in Phoenix are manageable, exposing
their lifecycle (configuration, startup/shutdown, etc) and
everything else you mark as manageable.</li>
</ul>
@@ -47,7 +47,7 @@
isolated from each other.</p>
<p>Phoenix provides simple XML configuration files that allow you to
- rapidly assemble a customised server applications from readily available
+ rapidly assemble a customised server application from readily available
components (called blocks).</p>
<p>Phoenix provides the following services to hosted applications:</p>
1.4.2.1 +12 -3 avalon-phoenix/src/xdocs/Attic/for-developers-a-future.xml
Index: for-developers-a-future.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/xdocs/Attic/for-developers-a-future.xml,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- for-developers-a-future.xml 16 Jun 2002 10:21:45 -0000 1.4
+++ for-developers-a-future.xml 23 Mar 2003 23:43:54 -0000 1.4.2.1
@@ -8,16 +8,25 @@
<body>
<section name="Introduction">
<p>
- A long term aim of Phoenix is to provide a platform that hosts multiple
third party applications written only in Java within a single virtual machine. The
Phoenix platform is currently hosted on an Operating System such as Unix, Windows or
Mac. It could function directly on top of a Java Operating System. A CPU combined
with a suitable amount of memory, a basic BIOS, a Kernal, a suitable JVM and runtime
library, could mount Phoenix and hosted server applications.
+ A long term aim of Phoenix is to provide a platform that hosts multiple
+ third party applications written only in Java within a single virtual
+ machine. The Phoenix platform is currently hosted on an Operating System
+ such as Unix, Windows or Mac. It could function directly on top of a
+ Java Operating System. A CPU combined with a suitable amount of memory,
+ a basic BIOS, a Kernal, a suitable JVM and runtime library, could mount
+ Phoenix and hosted server applications.
</p>
</section>
<section name="One step further">
<p>
- Imagine Sun making such a box under their own name or as Cobalt, using low
power chips from their own stable or perhaps a StrongARM. That machine could be rack
mounted like their current X1:
+ Imagine Sun making such a box under their own name or as Cobalt, using low
power chips from their
+ own stable or perhaps a StrongARM. That machine could be rack mounted like
their current X1:
</p>
<figure>
<title>Sun X1</title>
- <graphic srccredit="© Sun Microsystems"
fileref="http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg";
format="JPEG"/>
+ <graphic srccredit="© 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
1.1.2.1 +6 -6
avalon-phoenix/src/xdocs/Attic/for-developers-alternate-kernel.xml
Index: for-developers-alternate-kernel.xml
===================================================================
RCS file:
/home/cvs/avalon-phoenix/src/xdocs/Attic/for-developers-alternate-kernel.xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- for-developers-alternate-kernel.xml 30 Jun 2002 19:41:43 -0000 1.1
+++ for-developers-alternate-kernel.xml 23 Mar 2003 23:43:54 -0000 1.1.2.1
@@ -8,16 +8,16 @@
<body>
<section name="Introduction">
<p>
- Phoenix can launch with alternate kernels. Apart from the default
+ Phoenix can launch with alternate Kernels. Apart from the default
kernel which is suitable for deploying in live scenarios, we
supply a kernel which loads beanshell during startup.
</p>
</section>
- <section name="Beanshell enabled kernel">
+ <section name="Beanshell enabled Kernel">
<p>
This allows pretty much any anything to be done to applications
and blocks once started. As such it is not suitable for live
- deployment as it could be considered a bit of a hackers tool.
+ deployment as it could be considered a bit of a hacker's tool.
</p>
<p>
The supplied commands are getblock, prtapps, prtblocks, resumeapp,
@@ -26,15 +26,15 @@
interacting with the block's methods from its service.
</p>
<p>
- To create a beanshell capable kernel, place the bsh-1.2b6.jar from
+ To create a Beanshell capable kernel, place the bsh-1.2b6.jar from
<a href="http://www.beanshell.org/download.html";>here</a> in the
- lib directory of phoenix before building it. You will need to edit the
+ lib directory of Phoenix before building it. You will need to edit the
'beanshell.jars' and 'kernel.impl.class' parts of the ant.properties file.
You may also want to add your own convenience bsh scripts to the
src/bsh/ directory.
</p>
</section>
- <section name="Beanshell enabled, remotely accessible kernel">
+ <section name="Beanshell enabled, remotely accessible Kernel">
<p>
This is to-do.
</p>
1.7.2.3 +11 -11 avalon-phoenix/src/xdocs/Attic/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/xdocs/Attic/getting-started.xml,v
retrieving revision 1.7.2.2
retrieving revision 1.7.2.3
diff -u -r1.7.2.2 -r1.7.2.3
--- getting-started.xml 5 Mar 2003 07:34:05 -0000 1.7.2.2
+++ getting-started.xml 23 Mar 2003 23:43:54 -0000 1.7.2.3
@@ -36,7 +36,7 @@
<p>
To generate a full set of detailed API documentation for Avalon, go to the base
- directory of source distribution and run the appropriate build script for your
+ directory of the source distribution and run the appropriate build script for
your
platform with the parameter 'javadocs'.
<source><![CDATA[
@@ -48,11 +48,11 @@
</p>
</section>
-<section name="Run the HelloWorld example">
+<section name="Run the HelloWorld Example">
<p>
After you have successfully built Phoenix, you can verify that it
- has compiled correctly by running the HelloWorld demo Service Application.
+ has compiled correctly by running the HelloWorld Demo Service Application.
</p>
<p>
Firstly you will need to get the demo-helloword.sar file and drop it into
@@ -61,7 +61,7 @@
http://cvs.apache.org/viewcvs/avalon-apps/demo/</a>.
</p>
<p>
- Then fire up phoenix with the following command:
+ Then fire up Phoenix with the following command:
<source><![CDATA[
@@ -72,8 +72,8 @@
<p>
Next, fire up your favorite webbrowser and point it to http://localhost:8999/,
- where localhost is the network name of your machine ("localhost") should
- work on all windows platforms.<br />
+ where localhost is the network name of your machine "localhost" should
+ work on all Windows platforms.<br />
If all goes well, you will see something like the following:
<source><![CDATA[
@@ -101,11 +101,11 @@
<p>
This self contained kit could be considered a starter project for someone
wanting to make a
Phoenix compatible application. The idea is that you start with this skeleton
including
- Ant build script and then add in more and more as your se code to copy from
elsewhere.
+ an Ant build script and then add in more and more as your code, copying from
elsewhere.
</p>
<p>
- This also demonstrates that it is possible to make a server application that
is dual mode.
- Dual mode to us is the ability for the server application to run inside Phoenix
and to
+ This also demonstrates that it is possible to make a server application that is
dual mode.
+ Dual mode to us is the ability for the server application to run inside Phoenix
and
stand-alone from the command line. It is a little bit of a sleight of hand as
the codebase
would be zipped into two forms - the sar file for phoenix and a jar file for
standalone.
</p>
@@ -120,7 +120,7 @@
<li>phoenix-demo-server.sar - the server app in standalone form</li>
</ol>
- The Server app in standalone mode after being tested with the client app(see
below):
+ The Server app in standalone mode after being tested with the client app (see
below):
<source><![CDATA[
java -jar phoenix-demo-server.jar
@@ -149,7 +149,7 @@
</p>
<p>
Note - because of the need to make this dual mode, the PDK does not use
Cornerstone
- components. We normally recommend that people should reuse components from
cornerstone as
+ components. We normally recommend that people should reuse components from
Cornerstone as
the potential for sharing will be much higher.
</p>
</section>
No revision
No revision
1.1.2.3 +4 -4 avalon-phoenix/src/xdocs/mx/Attic/xdoctags.xml
Index: xdoctags.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/xdocs/mx/Attic/xdoctags.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- xdoctags.xml 16 Sep 2002 20:47:31 -0000 1.1.2.2
+++ xdoctags.xml 23 Mar 2003 23:43:54 -0000 1.1.2.3
@@ -13,10 +13,10 @@
</p>
<ul>
<li>
- its a lot faster than writing MXINFO files by hand
+ it's a lot faster than writing MXINFO files by hand
</li>
<li>
- its harder to make mistakes, since much of the data required for the
mxinfo file is
+ it's harder to make mistakes, since much of the data required for the
mxinfo file is
parsed out of the source code
</li>
<li>
@@ -129,7 +129,7 @@
<tr>
<td>Purpose</td>
<td>
- Marks the method as elible to be a management operation.
+ Marks the method as eligible to be a management operation.
</td>
</tr>
<tr>
@@ -264,7 +264,7 @@
<section name="Build Instructions">
<p>
To have mxinfo files generated as part as your ant build
- script, include a task like that this:
+ script, include a task like this:
</p>
<source>
<![CDATA[
No revision
No revision
1.4.2.4 +2 -2 avalon-phoenix/src/xdocs/stylesheets/Attic/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/xdocs/stylesheets/Attic/project.xml,v
retrieving revision 1.4.2.3
retrieving revision 1.4.2.4
diff -u -r1.4.2.3 -r1.4.2.4
--- project.xml 6 Mar 2003 01:32:31 -0000 1.4.2.3
+++ project.xml 23 Mar 2003 23:43:54 -0000 1.4.2.4
@@ -11,7 +11,7 @@
<menu name="Essentials">
<item name="Overview" href="/index.html"/>
<item name="Features" href="/features.html"/>
- <item name="Getting started" href="/getting-started.html"/>
+ <item name="Getting Started" href="/getting-started.html"/>
<item name="Download" href="http://avalon.apache.org/bindownload.cgi"/>
<item name="Install" href="/install.html"/>
</menu>
@@ -38,7 +38,7 @@
<menu name="For Developers">
<!-- <item name="Get Involved" href="/getinvolved.html"/> -->
<item name="Changes" href="/changes.html"/>
- <item name="Coding standards"
href="http://avalon.apache.org/code-standards.html"/>
+ <item name="Coding Standards"
href="http://avalon.apache.org/code-standards.html"/>
<item name="CVS Repositories"
href="http://jakarta.apache.org/site/cvsindex.html"/>
<item name="Mailing Lists"
href="http://jakarta.apache.org/site/mail.html"/>
<item name="TODO"
href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&product=Avalon&component=Phoenix"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
![http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg"](http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg"){kind=link}