The old scheduler was deprecated - see the bold text on
http://turbine.apache.org/turbine/turbine-2.3.3/services/scheduler-service.html
The replacement is the Fulcrum Quartz based scheduler -
http://turbine.apache.org/fulcrum/fulcrum-quartz/
Scott
On 25/01/11 7:09 AM, Ludwig Magnusson wrote:
I just thought I'd put this discussion in its own thread.
Actually, I had some time to experiment this evening and i JUST finished
putting in the old scheduler. It wasn't that hard. The tests pass (nothing
more tested though, I haven actually used this service much myself).
In the process I also changed the maven torque plugin configuration so that
the base classes are put in the target folder but the subclasses are put in
the source folder. If all files are put in the target folder like today, the
subclasses can't be versioned.
This was necessary since the subclasses of scheduled job are implemented
more than just the generated sources.
Anyway, I believe that I have it back to the way it was before and if you
want to look at it I can commit, but if you'd rather work on a new
implementation that's fine as well.
/Ludwig
From: Thomas Vandahl [mailto:[email protected]]
Sent: den 24 januari 2011 21:00
To: Turbine Developers List
Subject: Re: About me
The scheduler issue is more work than you might think. The previous
scheduler implementations used to build on the JobEntry/BaseJobEntry as
generated by Torque. This is no longer there and I'd rather keep it that
way. JobEntry is now an interface. I suggest to merge the NonPersistent
version if you will.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
