cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Fortress Migration Strategy
Date Tue, 14 Oct 2003 17:33:12 GMT
I have the Cocoon 2.2 repository checked out now, and I have printed out all the
code for the Cocoon processor and the CocoonComponentManager and
ExtendedServiceSelector, and all the other classes in the
org.apache.cocoon.components package (not all the child packages though).  I am
going to look over them and come up with how I plan to update things.  For some
of the work, there will be some "busy" work to add meta info to the Javadoc tags
in all the component implementations.  This will eliminate the need for a Cocoon
specific roles file.  We can still handle user's role files, though the current
format has changed.  We can add a compatibility layer for it, or we can
encourage cocoon users to upgrade.  Or we can do both.

That much is obvious.  The rest of it depends on the amount of custom things
that Cocoon is doing.  I believe we can add one or two custom lifecycle
extensions, and then we will be able to make the transition happen relatively

Are there other classes I have to worry about right now?  I will leave the
XSP for later, as that sounds like it will be made into a block.


"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin

View raw message