jvanzyl 02/03/10 18:44:42
Added: xdocs/common/status 02-08-2002.xml 02-15-2002.xml
02-22-2002.xml 03-01-2002.xml 03-08-2002.xml
Removed: xdocs/common/status 01-mar-2002.xml 08-feb-2002.xml
15-feb-2002.xml 22-feb-2002.xml
Log:
Changing the format of the dates to mm-dd-yyyy.xml to easily see
what's been missed.
Revision Changes Path
1.1 jakarta-turbine-site/xdocs/common/status/02-08-2002.xml
Index: 02-08-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 08 Feb 2002">
<p>
What's going on with Turbine these days? Well, quite a lot actually. We
were in a lull there for a while but things are back on track so I
thought I would try and report some of the work and changes that have
been going on recently.
</p>
</section>
<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>
<p>
<li>
Configuration: 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.
</li>
<li>
Exception: 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.
</li>
<li>
Factory: 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.
</li>
<li>
Introspection: 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.
</li>
<li>
JCS: 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="http://jpolycache.sourceforge.net";>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.
</li>
<li>
Lifecycle: 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="http://objectbridge.sourceforge.net";>ObjectBridge</a>
a subsystem for use in Turbine by providing a small wrapper
that implements the lifecycle interfaces.
</li>
<li>
Pool: This is essentially the PoolService refactored into
a component. Done so for the exact same reason the FactoryService
was turned into a component.
</li>
<li>
Resources: 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.
</li>
<li>
XO: This is currently an XML -> Bean mapper that takes an XML file
formatted in a common way and maps the content to a Java Bean.
Basically, this allows us to simply design our Bean, and
provided that the commons XML format is used no mapping rules
need to be created. The testbed has full examples, and the
Turbine 3.x pipeline descriptors are mapped using the XO
package. Again, we're working on full documentation though
the JavaDoc is fairly comprehensive.
</li>
</p>
</section>
<section name="Using DVSL for Documentation">
<p>
<a href="http://jakarta.apache.org/velocity/dvsl";>DVSL</a> is now
being used for the Turbine 3.x documentation as it is more flexible
and will allow the generation of PDF documents. Work was started in
the Velocity repository that transformed the xdocs into FOP documents
so I have started from that work to try and produce a good set of
PDF docs.
</p>
</section>
<section name="New Security Model">
<p>
Gonzalo and Eric are currently working on some ideas for a new
security model for Turbine 3.x. Anyone can view the work being
done by looking at the <b>rundata_security_changes</b> branch
in the <b>jakarta-turbine-3</b> repository.
</p>
</section>
<section name="RunData Reworking">
<p>
I am currently reworking the RunData system so that it can be
decoupled from Fulcrum and generally work in a more flexible manner.
We want to be able to use multiple variants of RunData in an
application, and we want each of those variants to house a
configurable set of tools: a cookie parser or a parameter parser
for example. This work needs to be finished before the security
models can be tried and tested. Hopefully the RunData work will
be finished next week sometime.
</p>
</section>
<section name="Turbine 3.x Pipeline">
<p>
The Pipeline in Turbine 3.x is now fully functional. Some
documentation on the pipeline has been created and it will be posted to
the site this weekend. The upshot of this change is that we now have
configurable request processing so an application can tailor its
pipeline(s) very easily to meet any requirements.
</p>
</section>
<section name="Introduction of Cactus">
<p>
The use of Cactus was introduced in the Turbine 3.x tree so that
changes can be tested easily. Jeff has also backported our
Cactus based testing framework to the 2.x branch. This is a
big step forward for us as we had virtually no testing
prior to this addition. Thanks a ton to Jeff for getting
this working!
</p>
</section>
<section name="More Consistent Build Pattern">
<p>
The build systems for Turbine 3.x, Turbine 2.x, Fulcrum, Torque
and Flux are all now basically the same. There is a new target
in each of the respective build files that will allow you to
download the JARs necessary for building the project. The TDK
has also been outfitted with this feature so developers interested
in helping improve the TDK can do so without having to hunt down
all the necessary JAR files. We hope that the addition of the JAR
downloader will help make it easier for people to participate
without having to build everything under the sun.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/status/02-15-2002.xml
Index: 02-15-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 15 Feb 2002">
<p>
Wow, we actually did this two weeks in a row :-) At any rate, here's a little
run down of what's been going on this week in Turbine.
</p>
</section>
<section name="New Committers">
<p>
James Taylor was added as a new committer this week. James has been
working on the Pipeline, has added some JGenerator renderers which
is very cool, and is generally helping out all over the place. Welcome
James!
</p>
</section>
<section name="Integration of the decoupled Torque in the TDK">
<p>
Martin has the decoupled Torque working with Turbine 2.x so he
is now working on integrating this work into the TDK. We are going
to officially deprecate the use of the coupled Torque, and when
we refer to Torque from now on we mean the decoupled Torque. The
Torque that exists in the 2.x tree is now officially road kill.
</p>
</section>
<section name="New Torque Tutorial!">
<p>
Pete Kazmier has written an excellent Torque Tutorial which is
now available <a
href="http://jakarta.apache.org/turbine/torque/tutorial.html";>here</a>.
This will certainly help a lot of users who have had some initial difficulty
in getting Torque set up and running. Thanks Pete!
</p>
</section>
<section name="Turbine Project Build System">
<p>
Jason has been working on a build system that can be used by all
Turbine projects. The goal is to have a single build.xml file that
can be used by all the builds. This is an effort to try and simplify
the maintenance overhead in all our projects now that we have decoupled
everything. We are going to move toward builds for each component in
Stratum and builds for each service in Fulcrum.
</p>
</section>
<section name="Security Model">
<p>
There has been a lot of discussion on the turbine-dev list
about the new security model for Turbine 3. Most recent
conversations have focused on what examples from JAAS could be
applied to Turbine Security. Check
<a
href="http://www.mail-archive.com/turbine-dev%40jakarta.apache.org/msg05759.html";>this
thread</a>
in the mail archive to see the details.
</p>
<p>
There was also some discussion about an LDAP implementation for Turbine 2.
See <a
href="http://www.mail-archive.com/turbine-dev%40jakarta.apache.org/msg05658.html";>this
thread</a>
for details. If that work gets completed, we will find a way
to include it in the Turbine 3 security model.
</p>
</section>
<section name="RunData Reworking">
<p>
The testbed is now working again in the <i>rundata_security_changes</i>
branch again. I'm not entirely happy with how it works yet but it's
getting there. Right now you can use a subclass of RunData but classes
the employ the use of this subclass must upcast in order to reach the
functionality within the subclass. I borrowed this method directly
from Jetspeed, but I would like to make something cleaner. I've got
some ideas and I'll post about them in next weeks status report.
</p>
</section>
<section name="Conversion of JCS logging to Commons Logging">
<p>
Using JCS as a test ground, James has implemented the use of
the Commons Logging package. We will still use log4j as our standard
back end logging mechanism but people who have chosen to use LogKit or Java
1.4
logging then they will easily be able to do so.
</p>
</section>
<section name="JCS Documentation">
<p>
Pete Kazmier started another great documentation effort by reworking
the current JCS documentation into our standard xdoc format. This will
definitely help people understand what a kick ass cache JCS really is :-)
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/status/02-22-2002.xml
Index: 02-22-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 22 Feb 2002">
<p>
</p>
</section>
<section name="New Committers">
<p>
Pete Kazmier was added as a new committer this week. Pete has been
doing tons of great documentation work, most notably in Torque and Stratum.
The documentation is greatly appreciated by all users so many thanks
to Pete! Welcome aboard!
</p>
<p>
Jauncarlo Arnez was added as a committer to work on Maven. Jaunco
donated a JavaCC-based RCS ,v file parser so that we can add CVS
log file analysis and continuous integration tools to Maven. Thanks
Jaunco!
</p>
<p>
Tom Copeland was added as a committer to work on Maven. Tom donated
importscrubber to Maven which is a tool that fully qualifies the import
statements in Java source files. The guts behind this tool is
dependency resolving mechanism that works on Java bytecode. We would
like to use this method to automatically resolve project dependencies
so that project descriptors with full dependencies can be made quickly
by projects wishing to work with Maven. Thanks Tom!
</p>
<p>
Stephane Baillinez was added as a new committer to work on Maven.
Stephane is an Ant developer, works on the Ant version of Gump and
has already sent more patches than I can deal with :-)
</p>
</section>
<section name="Progress on JCS">
<p>
Aaron and James have been refactoring some of the code and cleaning up
the tests. John McNally is also starting to look at how to integrate
JCS with Torque for object caching.
</p>
</section>
<section name="Progress on Maven">
<p>
Maven has been coming along quite well. There is now a site to
display what Maven can do, take a look <a
href="http://jakarta.apache.org/turbine/maven/";>here</a>.
In a nutshell we have:
</p>
<p>
<li>The project being built from a project descriptor</li>
<li>The project documentation being built from a project descriptor</li>
<li>Automatic generation of a change log based on CVS output</li>
<li>Source cross reference with links to Javadoc</li>
<li>Source metrics</li>
</p>
<p>
More information will be posted on the Turbine development list. But
the basic upshot is that with the creation of a project descriptor you
all the of what's listed above almost instantly.
</p>
</section>
<section name="Progress on Turbine 3.x">
<p>
Unfortunately not much went on this week with Turbine directory as
work on Maven took priority. Hopefully the use of Maven will help a
larger set of developers understand Turbine 3.x more quickly and
therefore spur on the development of Turbine 3.x.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/status/03-01-2002.xml
Index: 03-01-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 1 March 2002">
<p>
</p>
</section>
<section name="Turbine 2.2">
<p>
As it stands the last issue to deal with is making Fulcrum work
with Turbine 2.2. I will start dealing with this issue on Wednesday
building on what Martin has started and we are going to aim for
a beta within two weeks. Martin will continue working on Torque
so that by the time the beta rolls around Torque and Fulcrum will
be working well with Turbine 2.2. So we'll shoot for the 18th of
March.
</p>
</section>
<section name="Progress on Maven">
<p>
This is where most of the action is happening this week. The
documentation system is looking great, Jeff and Pete have tried
using Maven on a couple of small projects with success and we
hope to be able to use Maven for all the Turbine projects in the
next two weeks.
</p>
</section>
</body>
</document>
1.1 jakarta-turbine-site/xdocs/common/status/03-08-2002.xml
Index: 03-08-2002.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Turbine 3</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
<section name="Weekly Status Report: 1 March 2002">
<p>
</p>
</section>
<section name="Turbine 2.2">
<p>
As it stands the last issue to deal with is making Fulcrum work
with Turbine 2.2. I will start dealing with this issue on Wednesday
building on what Martin has started and we are going to aim for
a beta within two weeks. Martin will continue working on Torque
so that by the time the beta rolls around Torque and Fulcrum will
be working well with Turbine 2.2. So we'll shoot for the 18th of
March.
</p>
</section>
<section name="Progress on Maven">
<p>
This is where most of the action is happening this week. The
documentation system is looking great, Jeff and Pete have tried
using Maven on a couple of small projects with success and we
hope to be able to use Maven for all the Turbine projects in the
next two weeks.
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
