Siegfried,
I've put an issue in jira regarding the fortress service and assigned it
to me. I have a service working locally now and am just trying to build
fulcrum with the fortress meta tags so I can use them within fortress
for testing. I've also updated the maven-fortress-plugin so that it
works for me with my build system.
I'm away from tomorrow until Monday evening and will not be making any
further progress until then.
While I've been playing with fortress I have got no further switching
services. One question for you, are you aware of any reason that might
prevent us switching to the latest Avalon/excalibur dependencies for all
the fulcrum components. They are at RC3 now and a vote has been called
to release without change?
In answer to your question :
The follwoing services are still listed in the
TurbineResources.properties file from cvs head
IIRC the intention was to convert all of the services listed below to
fulcrum services and then use them in turbine 2.4. We will need to keep
the old service framework in place with no changes to functionality
while switching to the new services so that the old stuff can be
deprecated and only removed from cvs head after release of 2.4.
services.FactoryService.classname=org.apache.turbine.services.factory.TurbineFactoryService
services.PoolService.classname=org.apache.turbine.services.pool.TurbinePoolService
services.RunDataService.classname=org.apache.turbine.services.rundata.TurbineRunDataService
services.ServletService.classname=org.apache.turbine.services.servlet.TurbineServletService
services.AssemblerBrokerService.classname=org.apache.turbine.services.assemblerbroker.TurbineAssemblerBrokerService
services.SchedulerService.classname=org.apache.turbine.services.schedule.TurbineSchedulerService
services.XmlRpcService.classname=org.apache.turbine.services.xmlrpc.TurbineXmlRpcService
services.UniqueIdService.classname=org.apache.turbine.services.uniqueid.TurbineUniqueIdService
services.UploadService.classname=org.apache.turbine.services.upload.TurbineUploadService
services.SecurityService.classname=org.apache.turbine.services.security.db.DBSecurityService
services.PullService.classname=org.apache.turbine.services.pull.TurbinePullService
services.TemplateService.classname=org.apache.turbine.services.template.TurbineTemplateService
services.XSLTService.classname=org.apache.turbine.services.xslt.TurbineXSLTService
services.VelocityService.classname=org.apache.turbine.services.velocity.TurbineVelocityService
Could I suggest that we use jira to keep track of what is being done. It
looks like we could both be working on the fulcrum tree at the same
time. (unless you finish all the conversion over the next four days,
that is ;-) )
Regards,
Peter
Siegfried Goeschl wrote:
Hi folks,
are there any plans which existing Turbine services need to be migrated
for the next Turbine milestone release? Currently 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
This is rather a proof of concept than anything else ... :-( .... as
good condidates (where I can help) are XML-RPC and XSLT service
Cheers,
Siegfried Goeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
------------------------------
Peter Courcoux
Telephone : +44 (0)1923 661488
Mobile : 07880 605626
email : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
