commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons-sandbox/xo/xdocs index.xml
Date Wed, 08 May 2002 16:12:15 GMT
dion        02/05/08 09:12:15

  Modified:    xo/xdocs index.xml
  Removed stratum stuff
  Revision  Changes    Path
  1.2       +2 -110    jakarta-commons-sandbox/xo/xdocs/index.xml
  Index: index.xml
  RCS file: /home/cvs/jakarta-commons-sandbox/xo/xdocs/index.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.xml	16 Apr 2002 19:07:57 -0000	1.1
  +++ index.xml	8 May 2002 16:12:15 -0000	1.2
  @@ -5,121 +5,13 @@
       <author email="">Pete Kazmier</author>
       <author email="">Martin Poeschl</author>
       <author email="">Jason van Zyl</author>
  -    <title>Stratum</title>
  +    <title>XO</title>
  -    <section name="Stratum">
  -      <p>
  -        Stratum is the repository where we are trying to refactor a lot
  -        of the existing Turbine code into modularized components that
  -        can be used across all Turbine projects. The short term goal is
  -        refactoring for the purpose of clarifying the code for Turbine
  -        use, but after this has happened the goal is to move all the
  -        code, with thorough units tests of course, into the commons
  -        where we can share our code with the Jakarta community.
  -      </p>
  -      <p>
  -        There are several components in Stratum, most of the code
  -        originated in Turbine but there are some new additions. Here is
  -        a short run down of the components that will be available in
  -        Stratum:
  -      </p>
  +    <section name="XO">
  -        <tr>
  -          <td>Configuration</td>
  -          <td>
  -            This code originated in JServ, was brought into Turbine,
  -            moved to Velocity and improved, and then moved into the
  -            Commons as ExtendedProperties. The code in
  -            ExtendedProperties is a little unweildly and deals
  -            specifically with properties files. We wanted to use a
  -            general Configuration interface and allow the source of the
  -            values to vary. Right now we only have the properties file
  -            version working, but the XML configuration will soon work.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Exception</td>
  -          <td>
  -            This code has also wandered around a bit. It started in
  -            Turbine 2.x, and subsequently copied around into Torque,
  -            Fulcrum, and Turbine 3.x and eventually landed in the
  -            Commons Util package.  Again we wanted to clean it up a bit,
  -            make it work consistently throughout the Turbine code, make
  -            sure it will interoperate with chainable exceptions in 1.4
  -            and then put it back in the Commons.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Factory</td>
  -          <td>
  -            This is essentially the FactoryService refactored into a
  -            component. It's my feeling that factories are a fundamental
  -            aspect of an application and not a service. The example
  -            being Fulcrum where dynamic classloading cannot be performed
  -            very easily by the FactoryService within the core service
  -            code itself.  As a component the factory type behaviour
  -            provided can be used in a determined way anywhere, including
  -            the core of the Fulcrum service framework.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Introspection</td>
  -          <td>
  -            This is the introspector that was originally written for
  -            Velocity. It has been decoupled from Velocity and is being
  -            used in the XO mapper (see below). Once this code is cleaned
  -            up it can definitely be reused in Velocity.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>JCS</td>
  -          <td>
  -            This is the new caching system that we plan to use in all
  -            the Turbine projects. The package is maintained by Aaron
  -            Smuts and you can find a bit out about it <a
  -              href="">here</a>. Aaron
  -            has started documenting JCS and we'll get some comprehensive
  -            documentation up soon as I'm sure many people will be very
  -            interested in this package.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Lifecycle</td>
  -          <td>
  -            These are interfaces that we are starting to use in the
  -            Turbine code to provide a consistent way of dealing with
  -            various components like Torque and Fulcrum. By having Torque
  -            and Fulcrum implement these new lifecycle interfaces and
  -            teaching Turbine to deal with these interfaces we provide a
  -            new mechanism whereby any component can be made a subsystem
  -            very easily. So for example you could easily make <a
  -              href="">ObjectBridge</a>
  -            a subsystem for use in Turbine by providing a small wrapper
  -            that implements the lifecycle interfaces.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Pool</td>
  -          <td>
  -            This is essentially the PoolService refactored into a
  -            component. Done so for the exact same reason the
  -            FactoryService was turned into a component.
  -          </td>
  -        </tr>
  -        <tr>
  -          <td>Resources</td>
  -          <td>
  -            This package is a reworking of the resources package found
  -            in Velocity. The Velocity specifics have been removed and
  -            hopefully this package will provide facilities for full
  -            resource management.
  -          </td>
  -        </tr>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message