Hi Siegfried,
What I'm hoping to do is to get the Template (Velocity), AssemblerBroker
and Pull services (and any associated ones which I've missed) into
fulcrum and out of Turbine.
However, I agree it would be good to get as much input from others as we
can. Comments anyone?
It would be great to see you working on the Fortress stuff. I'm not a
Fortress wizard but might be able to help. With a few people working on
2.4 we will get a release much more quickly.
Peter
Hi Peter,
as far as I know the following Avalon-based services are currently used
within Turbine CVS HEAD
* org.apache.torque.avalon.Torque
* org.apache.fulcrum.cache.GlobalCacheService
* org.apache.fulcrum.mimetype.MimeTypeService
* org.apache.fulcrum.crypto.CryptoService
* org.apache.fulcrum.localization.LocalizationService
* org.apache.fulcrum.intake.IntakeService
* org.apache.fulcrum.factory.FactoryService
And those service are run within the YAAFI Avalon Container. But Fulcrum
has a lot more of released services being linked to Turbine such as
* XML-RPC Service
* an improved Security Service
* and a few more
Currently only a few non-critical Fulcrum services are used - I think
the PMCs should decide how many Fulcrum services should go into Turbine
2.4 .... Henning, Eric ?!
What I would like to do for a release is
* Migrate all existing Fulcrum services to use the Fortress Context
(that much about Avalon Container interoperability)
* Integrate or help integrating the upcoming Fortress release as
second Avalon container if it is not too much of a hassle (maybe a
Fortress wizard can lend a hand)
* Release a new XML-RPC Fulcrum Service based on the XML-RPC 2.0 and
push it into Turbine 2.4 (this is just a personal preference)
Cheers,
Siegfried Goeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
