> There's only 1 package to implement as a service before we can remove
> the JetspeedServlet: the daemon stuff.
I've been looking into this. There was talk of converting these to turbine
scheduled jobs and using the turbine scheduler. This is great, but will
require a database backend to hold the scheduled jobs, which in turn means
Jetspeed could not run without a database. John Thorhauer has created a
turbine scheduler that initializes from a properties file. We could use his
scheduler and implement it in Jetspeed or I was thinking of attempting to
merge this with the Turbine scheduler ( if possible ) and contrib back into
Turbine.
Converting the daemon implementations into scheduled jobs seems
straightforward. Any comments? Am I missing something?
jb
-----------------------------------------------------------------------
This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
