You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Ludwig Magnusson <lu...@itcatapult.com> on 2011/01/24 21:09:05 UTC
Scheduler
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:tv@apache.org]
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.
RE: Scheduler
Posted by Ludwig Magnusson <lu...@itcatapult.com>.
Yes, for this milestone was my idea as well.
IMHO, having M1 out and to be working on a scheduler implementation is
better than to be working on a scheduler implementation.
Since the name of the interface was JobEntry, the same as the class. I
renamed the interface to JobEntryInterface. This can be switched back when
the implementation is renewed.
/Ludwig
From: Thomas Vandahl [mailto:tv@apache.org]
Sent: den 24 januari 2011 21:23
To: Turbine Developers List
Subject: Re: Scheduler
On 24.01.11 21:09, Ludwig Magnusson wrote:
> 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.
Well, I didn't want to introduce more Torque dependencies than
necessary. However if we can agree that this would be for the milestone
only, I am fine with your solution. A new implementation using quartz
went south with my Macbook's hard disk a couple of months ago (No, no
daily backups...). It was not finished anyway.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
_____
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3400 - Release Date: 01/24/11
Re: Scheduler
Posted by Thomas Vandahl <tv...@apache.org>.
On 24.01.11 21:09, Ludwig Magnusson wrote:
> 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.
Well, I didn't want to introduce more Torque dependencies than
necessary. However if we can agree that this would be for the milestone
only, I am fine with your solution. A new implementation using quartz
went south with my Macbook's hard disk a couple of months ago (No, no
daily backups...). It was not finished anyway.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
RE: Scheduler
Posted by Ludwig Magnusson <lu...@itcatapult.com>.
There is a release of fulcrum-quartz out.
What is needed for 1.1.0?
/Ludwig
From: Scott Eade [mailto:seade@backstagetech.com.au]
Sent: den 24 januari 2011 23:06
To: Turbine Developers List
Subject: Re: Scheduler
The old scheduler was deprecated - see the bold text on
http://turbine.apache.org/turbine/turbine-2.3.3/services/scheduler-service.h
tml
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:tv@apache.org]
> 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: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
_____
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3400 - Release Date: 01/24/11
Re: Scheduler
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi folks,
from the Quartz point of view
+) jobs can be stored in a database but the database schema is
different (migration issue)
+) org.quartz.JobDataMap stores job specific fields, e.g. "task",
"email", "property"
The real question is - how much Torque code is bleeding into Turbine
Scheduler service usage (JobEntry derives from BaseJobEntry which
exposes a few public methods)
Cheers
Sigfried Goeschl
On 1/25/11 6:18 PM, Thomas Vandahl wrote:
> On 24.01.11 23:06, Scott Eade wrote:
>> 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/
> Yes, but the Quartz scheduler only knows about Jobs, it does not know
> about ScheduledJob modules. So a link between these two has to be
> created, if we want to support this in the future. In Addition, the
> TurbineSchedulerService allowed to add/update/remove jobs during runtime
> which I don't see in the fulcrum-quartz interface.
>
> The question is here: How much compatibility is required (or even possible)?
>
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Scheduler
Posted by Thomas Vandahl <tv...@apache.org>.
On 24.01.11 23:06, Scott Eade wrote:
> 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/
Yes, but the Quartz scheduler only knows about Jobs, it does not know
about ScheduledJob modules. So a link between these two has to be
created, if we want to support this in the future. In Addition, the
TurbineSchedulerService allowed to add/update/remove jobs during runtime
which I don't see in the fulcrum-quartz interface.
The question is here: How much compatibility is required (or even possible)?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Scheduler
Posted by Scott Eade <se...@backstagetech.com.au>.
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:tv@apache.org]
> 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: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org