avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From leosim...@apache.org
Subject cvs commit: jakarta-avalon/src/xdocs features.xml
Date Sat, 20 Apr 2002 13:34:15 GMT
leosimons    02/04/20 06:34:15

  Modified:    src/xdocs features.xml
  made lame feature doc somewhat less lame
  Revision  Changes    Path
  1.8       +76 -25    jakarta-avalon/src/xdocs/features.xml
  Index: features.xml
  RCS file: /home/cvs/jakarta-avalon/src/xdocs/features.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- features.xml	2 Apr 2002 11:12:00 -0000	1.7
  +++ features.xml	20 Apr 2002 13:34:15 -0000	1.8
  @@ -14,31 +14,82 @@
   <s1 title="Features">
  -  <p>
  -    <strong>This document is under construction!</strong><br />
  -    The Avalon framework provides the following features:
  -  </p>
  -  <ul>
  -<li> Component Oriented Programming framework to easily
  -  use and enforce COP in all your applications.</li>
  -<li> best-of-practice patterns so you're application will
  -  use a solid, proven design.</li>
  -<li> reusable Components already available for Avalon
  -  decrease your time-to-market because you don't have
  -  to reinvent the wheel.</li>
  -<li> several open source applications built on Avalon to
  -  use as inspiration for your own applications (Cocoon,
  -  JAMES, Jesktop, EAS, XCommander).</li>
  -<li> relatively small footprint for the core framework
  -  makes Avalon usable on almost every platform.</li>
  -<li> programmed for scalability and stability making it
  -  suitable for the Enterprise.</li>
  -<li> common tasks like thread, socket, class and configuration
  -  management are handled for you.</li>
  -<li> the closest thing to Rapid Enterprise Application
  -  Development yet.</li>
  -<li> pluggable functionality allows for high customization.</li>
  -  </ul>
  +  <p>The Avalon project is so large and broad in scope that it is not easy
  +  to provide a simple list of features in the form of "Avalon provides
  +  Component X which will fulfill role Y in your project Z perfectly".</p>
  +  <p>Most of Avalon is oriented towards server development (though many parts
  +  can be, and are, used in other software domains). As such, it delivers all
  +  those features server applications require (stability, performance, etc),
  +  and does so very well.</p>
  +  <s2 title="Avalon Framework">
  +    <p>At the very core of our project is the Avalon Framework subproject.
  +    This framework is very stable and in daily use in many applications, from
  +    straightforward desktop products to large scale enterprise applications.<br />
  +    After an initial difficult learning curve, this framework will help you
  +    create a better software architecture. In this way, it's role is as
  +    fundamental as, say Object-Oriented Programming or Design Patterns.</p>
  +    <p>All other avalon subprojects make use of the framework. This has allowed
  +    us to provide truly pluggable components which can be used in any
  +    programming environment without requiring gargantuan supporting applications.</p>
  +  </s2>
  +  <s2 title="Avalon Excalibur">
  +    <p>Avalon Excalibur provides you reusable components. Because our framework
  +    has been thought out so well, it becomes very easy to create quality
  +    components quickly. While many of the components in Excalibur are
  +    oriented towards server development (like a generic pooling implementation),
  +    others are very useful in other contexts as well (like utilities to help
  +    with internationalization).<br />
  +    Instead of listing the features of every single package here, I suggest you
  +    look at the
  +    <link href="http://jakarta.apache.org/avalon/excalibur">
  +      Excalibur project page
  +    </link> for more information.</p> 
  +  </s2>
  +  <s2 title="Avalon LogKit">
  +    <p>Avalon LogKit is a feature-rich logging package. It can be used as an
  +    Alternative to other logging packages like Jakarta's
  +    <link href="http://jakarta.apache.org/log4j">Log4J</link> or the (massively
  +    inferior)
  +    <link href="http://java.sun.com/j2se/1.4/docs/guide/util/logging/index.html">Logging
  +    included in JDK 1.4.<br />
  +    Please see the 
  +    <link href="http://jakarta.apache.org/avalon/logkit/features.html">
  +      Logkit Features document
  +    </link> for more information.</p>
  +  </s2>
  +  <s2 title="Avalon Phoenix">
  +    <p>Phoenix is a micro-kernel. It takes care of low level application details
  +    so you can focus on your unique requirments. While this may sound to you
  +    like a servlet or EJB container, phoenix has a very different scope. Where
  +    you can use EJBs to connect to a database, phoenix is the basis on which to
  +    run that database.<br />
  +    With that said, you may now start to see the phoenix edge: it provides all
  +    of the features that make you love Servlet Engines so much (and several
  +    more), without restricting you to the specific servlet use case. You can
  +    use Avalon Phoenix to run your servlet engine, database, and other server
  +    components, as well as your java-enabled desktop.</p>
  +    <p>Take a look at the
  +    <link href="http://jakarta.apache.org/avalon/phoenix">
  +      Phoenix project page
  +    </link> to learn how it manages to do all of this.</p>
  +  </s2>
  +  <s2 title="Avalon Applications">
  +    <p>Avalon Applications is a repository for Phoenix-enabled Applications.
  +    It contains a JDBC-compliant database, a Macromedia Flash-compatible XML socket
  +    server, and more. You'll also find a list of applications elsewhere on the
  +    web that run on phoenix. Go to the
  +    <link href="http://jakarta.apache.org/avalon/apps">
  +      Applications project page
  +    </link> to find out all about them.</p>
  +  </s2>

To unsubscribe, e-mail:   <mailto:avalon-cvs-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@jakarta.apache.org>

View raw message