donaldp 2003/02/22 18:04:02
Modified: src/documentation/content/xdocs getting-started.xml
install.xml tabs.xml
src/documentation/content/xdocs/bdg
making-phoenix-compatible-comps.xml
Log:
Jakarta --> AValon
Revision Changes Path
1.6 +2 -2
avalon-phoenix/src/documentation/content/xdocs/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file:
/home/cvs/avalon-phoenix/src/documentation/content/xdocs/getting-started.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- getting-started.xml 7 Feb 2003 15:35:58 -0000 1.5
+++ getting-started.xml 23 Feb 2003 02:04:02 -0000 1.6
@@ -17,7 +17,7 @@
This document provides developers with simple documentation for getting
started with Phoenix. For information about the overall structure of
Avalon Framework (on which Phoenix is based), please refer to the
- <link href="http://jakarta.apache.org/avalon/framework/index.html";>Framework
documentation</link>.
+ <link href="http://avalon.apache.org/framework/index.html";>Framework
documentation</link>.
</p>
<p>
@@ -57,7 +57,7 @@
<p>
Firstly you will need to get the demo-helloworld.sar file and drop it into
the apps directory of Phoenix. Currently it needs to be built from CVS -
- <link href="http://cvs.apache.org/viewcvs/jakarta-avalon-apps/demo/";>
+ <link href="http://cvs.apache.org/viewcvs/avalon-apps/demo/";>
http://cvs.apache.org/viewcvs/jakarta-avalon-apps/demo/</link>.
</p>
<p>
1.4 +3 -6 avalon-phoenix/src/documentation/content/xdocs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/documentation/content/xdocs/install.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install.xml 7 Feb 2003 15:35:58 -0000 1.3
+++ install.xml 23 Feb 2003 02:04:02 -0000 1.4
@@ -4,7 +4,7 @@
<header>
<title>Installation</title>
-
+
<authors><person name="Phoenix Documentation Team" email="[EMAIL
PROTECTED]"/></authors></header>
<body>
@@ -17,11 +17,8 @@
<p>
Everything required to run Phoenix and develop Phoenix based products comes
with the
- <link
href="http://jakarta.apache.org/builds/avalon/release";>distribution</link>. If
- you wish to help develop Avalon/Phoenix then it is recomended that you obtain
the full
- source tree from <link
href="http://jakarta.apache.org/getinvolved/cvsindex.html";>CVS</link>
- or from the <link
href="http://jakarta.apache.org/builds/avalon/nightly/";>nightly
- builds</link>.
+ distribution. If you wish to help develop Avalon/Phoenix then it is recomended
that you
+ obtain the full source tree from CVS or from the nightly builds.
</p>
</section>
1.3 +5 -5 avalon-phoenix/src/documentation/content/xdocs/tabs.xml
Index: tabs.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/documentation/content/xdocs/tabs.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tabs.xml 26 Nov 2002 23:26:52 -0000 1.2
+++ tabs.xml 23 Feb 2003 02:04:02 -0000 1.3
@@ -6,12 +6,12 @@
copyright="Foo"
xmlns:xlink="http://www.w3.org/1999/xlink";>
- <tab label="Framework"
href="http://jakarta.apache.org/avalon/framework/"/>
- <tab label="Excalibur"
href="http://jakarta.apache.org/avalon/excalibur/"/>
- <tab label="Cornerstone"
href="http://jakarta.apache.org/avalon/cornerstone/"/>
+ <tab label="Framework" href="http://avalon.apache.org/framework/"/>
+ <tab label="Excalibur" href="http://avalon.apache.org/excalibur/"/>
+ <tab label="Cornerstone" href="http://avalon.apache.org/cornerstone/"/>
<tab label="Phoenix" dir="/"/>
- <tab label="Apps" href="http://jakarta.apache.org/avalon/apps/"/>
- <tab label="Logkit" href="http://jakarta.apache.org/avalon/logkit/"/>
+ <tab label="Apps" href="http://avalon.apache.org/apps/"/>
+ <tab label="Logkit" href="http://avalon.apache.org/logkit/"/>
<!-- Add new tabs here, eg:
<tab label="How-Tos" dir="community/howto/"/>
<tab label="XML Site" dir="xml-site/"/>
1.4 +2 -2
avalon-phoenix/src/documentation/content/xdocs/bdg/making-phoenix-compatible-comps.xml
Index: making-phoenix-compatible-comps.xml
===================================================================
RCS file:
/home/cvs/avalon-phoenix/src/documentation/content/xdocs/bdg/making-phoenix-compatible-comps.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- making-phoenix-compatible-comps.xml 2 Dec 2002 08:07:34 -0000 1.3
+++ making-phoenix-compatible-comps.xml 23 Feb 2003 02:04:02 -0000 1.4
@@ -33,12 +33,12 @@
</p>
</section>
<section><title>Inversion of Control Pattern</title>
- <p>The IoC pattern is described <link
href="http://jakarta.apache.org/avalon/framework/inversion-of-control.html";>
+ <p>The IoC pattern is described <link
href="http://avalon.apache.org/framework/inversion-of-control.html";>
here</link>. This means for Phoenix avoiding static concepts including
loggers.</p>
</section>
<section><title>Separation of interface and implementation</title>
<p>
- The separation of interface/implementation pattern is described <link
href="http://jakarta.apache.org/avalon/framework/separation-of-interface-and-implementation.html";>here</link>.
+ The separation of interface/implementation pattern is described <link
href="http://avalon.apache.org/framework/separation-of-interface-and-implementation.html";>here</link>.
For Phoenix this means we can (if done completely) mount the
implementation jar in place where hosted client components (beans, servlets etc) can
use the API, but not see the implementation. We can also reimplement or wrap
bits of the implementation. For example we could write a pluggable
implementation that could, for a certain API
journal some methods, but still delegate to the real implementation.
Which pluggable implementation is used by Phoenix when it
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
