huw         2003/02/22 21:52:05

  Modified:    src/documentation/content/xdocs index.xml
  Log:
  updated links to point to avalon.apache.org
  
  Revision  Changes    Path
  1.4       +10 -10    avalon-site/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/avalon-site/src/documentation/content/xdocs/index.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- index.xml 3 Feb 2003 15:43:38 -0000       1.3
  +++ index.xml 23 Feb 2003 05:52:05 -0000      1.4
  @@ -21,7 +21,7 @@
         <p>
         Having said that, what Avalon 'is', is a framework that allows 
components of varying
         scale to be created, managed via a specific set of
  -      <link 
href="http://jakarta.apache.org/avalon/framework/reference-the-lifecycle.html";>lifecycle</link>
 methods,
  +      <link 
href="http://avalon.apache.org/framework/reference-the-lifecycle.html";>lifecycle</link>
 methods,
         and used in an application. While Avalon is geared towards server-side 
applications,
         it is not limited to such, and is quite flexible.
         </p>
  @@ -29,7 +29,7 @@
         The scope of usage for Avalon is quite broad. You may only want to 
create custom, application
         specific components that can be managed in a well defined manner, or 
you may want to use the many
         components and services available with the
  -      <link 
href="http://jakarta.apache.org/avalon/excalibur/index.html";>Excalibur</link>
  +      <link 
href="http://avalon.apache.org/excalibur/index.html";>Excalibur</link>
         sub-project, or use complete applications, such as FTP or a web 
server, in a server oriented
         container such as Phoenix. What this means to you is that you can use 
only what you need to use,
         and you can scale your usage of Avalon as your application needs grow.
  @@ -48,7 +48,7 @@
           The Avalon Team is proud to announce a new whitepaper that covers how
           to develop with Avalon. It covers the Framework, and touches on the
           LogKit and Excalibur. You can find
  -        <link 
href="http://jakarta.apache.org/avalon/developing/index.html";>Developing with 
Apache Avalon</link>
  +        <link 
href="http://avalon.apache.org/developing/index.html";>Developing with Apache 
Avalon</link>
           on this site.
         </p>
       </section>
  @@ -61,7 +61,7 @@
         <section>
   <title>Framework</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/framework/index.html";>Framework</link> 
provides a specification of
  +          <link 
href="http://avalon.apache.org/framework/index.html";>Framework</link> provides 
a specification of
             design patterns and rules in the form of interfaces. Also provided 
are default
             implementations of those interfaces.
           </p>
  @@ -77,16 +77,16 @@
         <section>
   <title>Excalibur</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/excalibur/index.html";>Excalibur</link> 
is a collection of
  +          <link 
href="http://avalon.apache.org/excalibur/index.html";>Excalibur</link> is a 
collection of
             implementations and common code based on and implementing the
  -          <link 
href="http://jakarta.apache.org/avalon/framework/index.html";>Avalon 
Framework</link>.
  +          <link href="http://avalon.apache.org/framework/index.html";>Avalon 
Framework</link>.
           </p>
         </section>
   
         <section>
   <title>Phoenix</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/phoenix/index.html";>Phoenix</link> is a 
server oriented
  +          <link 
href="http://avalon.apache.org/phoenix/index.html";>Phoenix</link> is a server 
oriented
             application server. Applications and services that conform to the 
framework
             rules can be hosted in Phoenix. The application server manages the 
applications
             classloader, security and logging needs. It also provides a 
JMX-based management
  @@ -97,7 +97,7 @@
         <section>
   <title>Cornerstone</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/cornerstone/index.html";>Cornerstone</link>
 is a repository
  +          <link 
href="http://avalon.apache.org/cornerstone/index.html";>Cornerstone</link> is a 
repository
             for what we call <link 
href="phoenix/what-is-a-block.html">blocks</link>,
             which provide services vital to server applications. The blocks 
include blocks for
             services such as scheduling and socket management.
  @@ -107,7 +107,7 @@
         <section>
   <title>Applications</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/apps/index.html";>Applications</link> is 
a repository of
  +          <link 
href="http://avalon.apache.org/apps/index.html";>Applications</link> is a 
repository of
             Phoenix blocks.  Some are simple, self-contained demos of Phoenix 
applications,
             others are complete standalone products, and a few are ambitious 
works in progress.
             If you are looking for a starting point for a Phoenix block or a 
complete server,
  @@ -118,7 +118,7 @@
         <section>
   <title>LogKit</title>
           <p>
  -          <link 
href="http://jakarta.apache.org/avalon/logkit/index.html";>LogKit</link> is the 
preferred logging toolkit
  +          <link 
href="http://avalon.apache.org/logkit/index.html";>LogKit</link> is the 
preferred logging toolkit
             used by the Avalon sub-projects.</p>
          <p>
          It is quite possible to use the other avalon sub-projects without 
committing to logkit.
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to