Jason van Zyl wrote: > Hi, > > All users that have responded on the list want to wait for the decoupled > versions of torque and fulcrum to be available for use in 2.x before we > release. We have discussed this briefly in IRC but how about the following > for a plan. > > i) Introduction of lifecycle interfaces in org.apache.stratum.lifecycle. > These are direct copies of Avalon's lifecycle interfaces as I see no point > making signatures that aren't compatible, we may never use Avalon but I > could definitely see some of their lifecycle interfaces moving into the > commons eventually. > > ii) Make Torque and Fulcrum implement these lifecycle interfaces so that > they can be manipulated in the same fashion with respect to configuration > and initialization. > > iii) Code would be added to both t3 and t2 so that subsystems implementing > these lifecycle interfaces can be dealt with. The result will be the > pluggability of large subsystems like services frameworks and persistence > frameworks. So someone could use another services framework or persistence > tool with t3 a lot more easily. The upshot is also that Torque will be used > directly and we'll get rid of the DatabaseService all together. > > Martin is willing to work on the Turbine code, and I can work on the Fulcrum > code and making the necessary changes to the turbine code. > > This is the only way I can see to allow us to use the decoupled codebases in > both t2 and t3. > > In Tambora, as I imagine with many 2.x projects, we want to help contribute > toward the decoupled code bases but we can't move away from 2.x for a while > so Martin and myself can definitely put some time into this as it is > important for Tambora. In a brief chat with Martin we decided that we could > get most of the work and testing done in three weeks if we start today. > > I think as soon as we can get rid of the couple code bases the better and it > appears that users are willing to wait, as they've waited this long already. > > So I'm an obvious > > +1
+1 martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
