You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by ha...@apache.org on 2003/03/16 23:22:19 UTC
cvs commit: avalon-apps/site/src/xdocs appselsewhere.xml appsincvs.xml index.xml todo.xml
hammant 2003/03/16 14:22:19
Modified: demo/src/xdocs demo-helloworld.xml demo-lifecycle.xml
ftpserver/src/xdocs conf.xml
sevak/src/xdocs index.xml
site/src/xdocs appselsewhere.xml appsincvs.xml index.xml
todo.xml
Log:
some links fixed
Revision Changes Path
1.9 +2 -2 avalon-apps/demo/src/xdocs/demo-helloworld.xml
Index: demo-helloworld.xml
===================================================================
RCS file: /home/cvs/avalon-apps/demo/src/xdocs/demo-helloworld.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- demo-helloworld.xml 16 Mar 2003 21:12:34 -0000 1.8
+++ demo-helloworld.xml 16 Mar 2003 22:22:19 -0000 1.9
@@ -100,7 +100,7 @@
Familiarity with Ant and it's build script would be a good place to start. After learning how Cornerstone compiles and jars the demos would be a good second step. Thirdly, as I've done before, take the demos out of Cornerstone, delete classes and xml not relating to the HelloWorld server and rename from HelloWorld to whatever suits you. I import into the lib dir avalon-cornerstone-compilation-0.x.jar to allow things that use it to compile. I also import cornerstone-0.x.bar to the same place to allow it's inclusion in the sar file being made. The build xml file even contains a target that allow you to install the freshly made sar file into a nearby Avalon installation - "build install", though for development you'll initially only be running "build" and "build clean".
</p>
<p>
- As a secondary process, it would be handy to learn xdocs (the technology that allows the creation of these book pages). You're copying cornerstone to be (after some selective trimming) the foundation stone for new server app, so you might as well take adavantage of all it's templates.. "build xdocs" and look in build/docs. All the Apache java based projects do this and then copy that to the website. The project I'm involved with <link href="http://www.jesktop.org">Jesktop</link> does too.
+ As a secondary process, it would be handy to learn xdocs (the technology that allows the creation of these book pages). You're copying cornerstone to be (after some selective trimming) the foundation stone for new server app, so you might as well take adavantage of all it's templates.. "build xdocs" and look in build/docs. All the Apache java based projects do this and then copy that to the website. The project I'm involved with <a href="http://www.jesktop.org">Jesktop</a> does too.
</p>
</section>
</body>
1.3 +2 -2 avalon-apps/demo/src/xdocs/demo-lifecycle.xml
Index: demo-lifecycle.xml
===================================================================
RCS file: /home/cvs/avalon-apps/demo/src/xdocs/demo-lifecycle.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- demo-lifecycle.xml 16 Mar 2003 21:12:34 -0000 1.2
+++ demo-lifecycle.xml 16 Mar 2003 22:22:19 -0000 1.3
@@ -13,7 +13,7 @@
<body>
<section name="Introduction">
<p>
- The lifecycle demo shows only the calling of the lifecycle methods under Phoenix control. This app has meaning when you consider the <link href="http://jakarta.apache.org/avalon/framework/reference-the-lifecycle.html">lifecycle</link> page.
+ The lifecycle demo shows only the calling of the lifecycle methods under Phoenix control. This app has meaning when you consider the <a href="http://jakarta.apache.org/avalon/framework/reference-the-lifecycle.html">lifecycle</a> page.
</p>
<p>
Do not forget that the lifecycle methods are optional. You cann implement all of them, as this demo does, some or none of them.
1.3 +2 -2 avalon-apps/ftpserver/src/xdocs/conf.xml
Index: conf.xml
===================================================================
RCS file: /home/cvs/avalon-apps/ftpserver/src/xdocs/conf.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- conf.xml 16 Mar 2003 21:35:56 -0000 1.2
+++ conf.xml 16 Mar 2003 22:22:19 -0000 1.3
@@ -153,11 +153,11 @@
</li>
<li>
<strong>DbUserManager</strong> - databased based user manager.
- Please see <link href="jdbc.html">"DB Support"</link> for more details.
+ Please see <a href="jdbc.html">"DB Support"</a> for more details.
</li>
<li>
<strong>LdapUserManager</strong> - LDAP based user manager.
- Please see <link href="ldap.html">"LDAP Support"</link> for more details.
+ Please see <a href="ldap.html">"LDAP Support"</a> for more details.
</li>
</ul>
<table>
1.6 +3 -3 avalon-apps/sevak/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-apps/sevak/src/xdocs/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 16 Mar 2003 21:35:57 -0000 1.5
+++ index.xml 16 Mar 2003 22:22:19 -0000 1.6
@@ -15,8 +15,8 @@
<section name="Introduction">
<p>
Sevak is a wrapper for Tomcat Catalina server in a Phoenix machine.
- <link href="http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/">
- http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/</link>
+ <a href="http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/">
+ http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/</a>
It launches Catalina under Phoenix control in embedded mode.
</p>
</section>
1.7 +11 -11 avalon-apps/site/src/xdocs/appselsewhere.xml
Index: appselsewhere.xml
===================================================================
RCS file: /home/cvs/avalon-apps/site/src/xdocs/appselsewhere.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- appselsewhere.xml 16 Mar 2003 21:35:57 -0000 1.6
+++ appselsewhere.xml 16 Mar 2003 22:22:19 -0000 1.7
@@ -20,14 +20,14 @@
<section name="JAMES">
<p>
JAMES is an email and news server ad has been under development for a number of years.
- See <link href="http://jakarta.apache.org/james">http://jakarta.apache.org/james</link>.
+ See <a href="http://jakarta.apache.org/james">http://jakarta.apache.org/james</a>.
It is hosted at Jakarta, and is Apache licensed.
</p>
</section>
<section name="Jo! Web Server">
<p>
Hendrik Schreiber has an excellent web server that is servlet capable. It is hosted at
- <link href="http://www.tagtraum.com/jo.html">http://www.tagtraum.com/jo.html</link> and
+ <a href="http://www.tagtraum.com/jo.html">http://www.tagtraum.com/jo.html</a> and
comes with a block for use within Phoenix. As a demo, it is possible to build a SAR
file to see the default webapp of Jo! running under Phoenix control. Jo! is Open-Source
(LGPL license). We also like to point you towards the Sevak project. It is the formal
@@ -37,38 +37,38 @@
<section name="JabaServer">
<p>
Alexis Agahi and Vinaysahil Chandran have migrated JabaServer (an open-source Java
- implementation of Jabber) to be Phoenix dependant. See <link href="http://www.javajabber.net/">
- http://www.javajabber.net/</link>. JabberServer is BSD license.
+ implementation of Jabber) to be Phoenix dependant. See <a href="http://www.javajabber.net/">
+ http://www.javajabber.net/</a>. JabberServer is BSD license.
</p>
</section>
<section name="Enterprise Object Broker (EOB)">
<p>
This is an application server that uses the Jo! block. It is not J2EE compatible.
- See <link href="http://www.enterpriseobjectbroker.org">http://www.enterpriseobjectbroker.org</link>.
+ See <a href="http://www.enterpriseobjectbroker.org">http://www.enterpriseobjectbroker.org</a>.
EOB is Apache licensed.
</p>
</section>
<section name="Jesktop">
<p>
- This is a desktop GUI that sits on Phoenix. See <link href="http://www.jesktop.com">http://www.jesktop.com</link>.
+ This is a desktop GUI that sits on Phoenix. See <a href="http://www.jesktop.com">http://www.jesktop.com</a>.
This Jesktop reference implementation is Apache licensed.
</p>
</section>
<section name="PhoenixJMS">
<p>
A JMS implementation hosted at SourceForge.
- See <link href="http://sourceforge.net/projects/phoenixjms">http://sourceforge.net/projects/phoenixjms</link>
+ See <a href="http://sourceforge.net/projects/phoenixjms">http://sourceforge.net/projects/phoenixjms</a>
</p>
</section>
<section name="Hypersonic SQL">
<p>
- A wrapper that allows Hsqldb (project <link href="http://sf.net/prohjects/hsqldb">http://sf.net/prohjects/hsqldb</link>)
- to be served from inside Phoenix. See <link href="http://jakarta.apache.org/avalon/apps/apps/hsql/index.html">apps/hsql</link>
+ A wrapper that allows Hsqldb (project <a href="http://sf.net/prohjects/hsqldb">http://sf.net/prohjects/hsqldb</a>)
+ to be served from inside Phoenix. See <a href="http://jakarta.apache.org/avalon/apps/apps/hsql/index.html">apps/hsql</a>
</p>
</section>
<section name="DeeBee">
<p>
- Also under infrequent development, an ambitious JDBC compliant RDBMS. See <link href="http://spice.sf.net">http://spice.sf.net</link>
+ Also under infrequent development, an ambitious JDBC compliant RDBMS. See <a href="http://spice.sf.net">http://spice.sf.net</a>
</p>
</section>
</section>
1.10 +10 -10 avalon-apps/site/src/xdocs/appsincvs.xml
Index: appsincvs.xml
===================================================================
RCS file: /home/cvs/avalon-apps/site/src/xdocs/appsincvs.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- appsincvs.xml 16 Mar 2003 21:35:57 -0000 1.9
+++ appsincvs.xml 16 Mar 2003 22:22:19 -0000 1.10
@@ -5,9 +5,9 @@
<document>
<properties>
<title>Avalon Applications - Apps in Avalon CVS</title>
- <linkuthors>
+ <authors>
<person name="Paul Hammant" email="Paul_Hammant@yahoo.com"/>
- </linkuthors>
+ </authors>
</properties>
<body>
<section name="Applications in the avalon-apps project">
@@ -16,37 +16,37 @@
</p>
<section name="Demos">
<p>
- A simple "Hello world" demo. See <link href="http://avalon.apache.org/apps/apps/demo/index.html">apps/demo</link>
+ A simple "Hello world" demo. See <a href="http://avalon.apache.org/apps/apps/demo/index.html">apps/demo</a>
</p>
</section>
<section name="FTP Server">
<p>
- A server that serves standands compliant FTP services. See <link href="http://avalon.apache.org/apps/apps/ftpserver/index.html">apps/ftpserver</link>
+ A server that serves standands compliant FTP services. See <a href="http://avalon.apache.org/apps/apps/ftpserver/index.html">apps/ftpserver</a>
</p>
</section>
<section name="HTTP Proxy">
<p>
- A simple demo that is a proxy server for web browsers. See <link href="http://avalon.apache.org/apps/apps/httpproxy/index.html">apps/httpproxy</link>
+ A simple demo that is a proxy server for web browsers. See <a href="http://avalon.apache.org/apps/apps/httpproxy/index.html">apps/httpproxy</a>
</p>
</section>
<section name="Overlord">
<p>
- An in development content gathering server. See <link href="http://avalon.apache.org/apps/apps/overlord/index.html">apps/overlord</link>
+ An in development content gathering server. See <a href="http://avalon.apache.org/apps/apps/overlord/index.html">apps/overlord</a>
</p>
</section>
<section name="Sevak">
<p>
- A web server service. The initial implementation wraps Cataliana. See <link href="http://avalon.apache.org/apps/apps/sevak/index.html">apps/sevak</link>
+ A web server service. The initial implementation wraps Cataliana. See <a href="http://avalon.apache.org/apps/apps/sevak/index.html">apps/sevak</a>
</p>
</section>
<section name="SimpleServer">
<p>
- A simple demonstration of a Phoenix dependant server. See <link href="http://avalon.apache.org/apps/apps/simpleserver/index.html">apps/simpleserver</link>
+ A simple demonstration of a Phoenix dependant server. See <a href="http://avalon.apache.org/apps/apps/simpleserver/index.html">apps/simpleserver</a>
</p>
</section>
<section name="XCommander">
<p>
- A server that resonds to XML commands from its clients. See <link href="http://avalon.apache.org/apps/apps/xcommander/index.html">apps/xcommander</link>
+ A server that resonds to XML commands from its clients. See <a href="http://avalon.apache.org/apps/apps/xcommander/index.html">apps/xcommander</a>
</p>
</section>
</section>
1.12 +6 -6 avalon-apps/site/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-apps/site/src/xdocs/index.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- index.xml 16 Mar 2003 21:35:57 -0000 1.11
+++ index.xml 16 Mar 2003 22:22:19 -0000 1.12
@@ -13,7 +13,7 @@
<section name="Introduction">
<p>
The apps Avalon sub-project is a repository of applications that run on top of
- the <link href="http://avalon.apache.org/phoenix/index.html">Phoenix</link> application kernel.
+ the <a href="http://avalon.apache.org/phoenix/index.html">Phoenix</a> application kernel.
Each of these applications applications are at different stages of development
and evolution. Some of the "applications" are thin wrappers around existing
products that make them capable of being managed from within Phoenix. While
@@ -45,21 +45,21 @@
See the <strong>left margin</strong> of this page for the links to applications in
Avalon's CVS and elsewhere. The applications listed there are
downloadable from
- <link href="http://jakarta.apache.org/builds/avalon/TODO">here</link>
+ <a href="http://jakarta.apache.org/builds/avalon/TODO">here</a>
and can be dropped into the your handy Phoenix server.
</p>
</section>
<section name="Basics on Phoenix application environment">
<p>
For a quick graphical view of Phoenix hosting multiple server applications, see
- the diagrams on the <link href="http://avalon.apache.org/phoenix/">
- Phoenix main page.</link>. Phoenix takes multiple complete applications in a
+ the diagrams on the <a href="http://avalon.apache.org/phoenix/">
+ Phoenix main page.</a>. Phoenix takes multiple complete applications in a
zip file with a 'sar' suffix and mounts them all at the same time in the
same virtual machine
</p>
<p>
You will also want to understand the Avalon Framework interfaces.
- <link href="http://avalon.apache.org/framework/">here</link>.
+ <a href="http://avalon.apache.org/framework/">here</a>.
Particularly, you will need to read up on the <strong>central patterns</strong>,
and the <strong>lifecycle aspects of components</strong>.
</p>
1.7 +15 -15 avalon-apps/site/src/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/avalon-apps/site/src/xdocs/todo.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- todo.xml 16 Mar 2003 21:35:57 -0000 1.6
+++ todo.xml 16 Mar 2003 22:22:19 -0000 1.7
@@ -60,8 +60,8 @@
DNS is the central scheme by which machines on the internet are looked up.
</p>
<p>
- DNS in Java has been done already. See <link href="http://sourceforge.net/projects/dnsjava/">
- http://sourceforge.net/projects/dnsjava/</link>. This is LGPL licensed software so could not
+ DNS in Java has been done already. See <a href="http://sourceforge.net/projects/dnsjava/">
+ http://sourceforge.net/projects/dnsjava/</a>. This is LGPL licensed software so could not
be hosted by Apache if a port were undertaken. It might be best to start afresh as there are
so many possibilities for abstractions and configurable concepts (forwarding DNS impls, DNSlet,
Some using persistence stores, some using databases
@@ -97,8 +97,8 @@
A Heavy crypto mechanism to provide secure access to a remote client.
</p>
<p>
- See <link href="http://www.openssh.org/java.html">
- http://www.openssh.org/java.html</link> for details about available java tools. Mindterm, listed
+ See <a href="http://www.openssh.org/java.html">
+ http://www.openssh.org/java.html</a> for details about available java tools. Mindterm, listed
there, would be a good candidate, but it forked and went in two directions (1) Commercial/closed (2)
GPL. The latter is not allowed to import ASF licensed code ("Block" being an example) so could
not be ported. A from scratch impl would be best here.
@@ -109,7 +109,7 @@
Ancient and insecure (over TCP/IP) protocol for having shell access to a computer.
</p>
<p>
- See <link href="http://telnetd.sourceforge.net/">http://telnetd.sourceforge.net/</link>.
+ See <a href="http://telnetd.sourceforge.net/">http://telnetd.sourceforge.net/</a>.
This project is appraising Phoenix and seeing if they can make a migration to it.
</p>
</section>
@@ -118,7 +118,7 @@
For interoperation with a Windows network, CIFS is the thing.
</p>
<p>
- See <link href="http://jcifs.samba.org/">http://jcifs.samba.org/</link>.
+ See <a href="http://jcifs.samba.org/">http://jcifs.samba.org/</a>.
This is LGPL licensed so could be ported to Avalon, but not hosted at Apache. As always, a fresh
start might be best.
</p>
@@ -134,7 +134,7 @@
LDAP - a location of services people, orgs, resources protocol.
</p>
<p>
- See <link href="http://sourceforge.net/projects/javaldap/">http://sourceforge.net/projects/javaldap/</link>
+ See <a href="http://sourceforge.net/projects/javaldap/">http://sourceforge.net/projects/javaldap/</a>
for a Java implementation. Unfortunately, it's license is unsuitable for compilation against Apache
foundation classes.
</p>
@@ -144,10 +144,10 @@
RADIUS - A server to authenticate dial-in users.
</p>
<p>
- See <link href="http://sourceforge.net/projects/jradius/">http://sourceforge.net/projects/jradius/</link>
+ See <a href="http://sourceforge.net/projects/jradius/">http://sourceforge.net/projects/jradius/</a>
for a Java implementation. Unfortunately, it's license is unsuitable for compilation against Apache
- foundation classes. The RFCs for RADIUS are <link href="http://www.ietf.org/rfc/rfc2865.txt?number=2865">2865</link>
- and <link href="http://www.ietf.org/rfc/rfc2868.txt?number=2868">2868</link>.
+ foundation classes. The RFCs for RADIUS are <a href="http://www.ietf.org/rfc/rfc2865.txt?number=2865">2865</a>
+ and <a href="http://www.ietf.org/rfc/rfc2868.txt?number=2868">2868</a>.
</p>
</section>
<section name="Finger">
@@ -156,9 +156,9 @@
used for several things over the years including passing of PGP public keys and "are you at your desk" type of thing.
</p>
<p>
- An essential read is <link href="http://www-cse.ucsd.edu/users/bsy/coke.history.txt">
- http://www-cse.ucsd.edu/users/bsy/coke.history.txt</link>. The RFC for finger is
- <link href="http://www.ietf.org/rfc/rfc1288.txt?number=1288">1288</link>.
+ An essential read is <a href="http://www-cse.ucsd.edu/users/bsy/coke.history.txt">
+ http://www-cse.ucsd.edu/users/bsy/coke.history.txt</a>. The RFC for finger is
+ <a href="http://www.ietf.org/rfc/rfc1288.txt?number=1288">1288</a>.
</p>
</section>
<section name="Internet Relay Chat">
@@ -185,9 +185,9 @@
</section>
<section name="JDBC compliant DBMS">
<p>
- We have a block that launches <link href="http://www.sourceforge.net/projects/hsqldb">HypersonicSQL</link>
+ We have a block that launches <a href="http://www.sourceforge.net/projects/hsqldb">HypersonicSQL</a>
already, but in November 2001 we started a new DBMS called
- <link href="http://jakarta.apache.org/avalon/apps/apps/db/index.html">AvalonDB</link> at Apache.
+ <a href="http://jakarta.apache.org/avalon/apps/apps/db/index.html">AvalonDB</a> at Apache.
</p>
</section>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org