Re: Scheduled Actions
Re: Scheduled Actions
- Subject: Re: Scheduled Actions
- From: Alexis Tual <email@hidden>
- Date: Thu, 31 Mar 2011 14:06:55 +0200
Bonjour Philippe,
That's interesting, we've done something similar but very specific to our ERP (several apps - one BDD) :
- modeling and persisting of scheduled actions with our own eomodel
- scheduling with quartz : one scheduler with RAMJobStore for an entire app, that's a limitation due to our architecture
How did you handle quartz scheduler with WO multi-instances ?
If your persist your own scheduled actions in db, 1 scheduler with RAMJobStore per webapp instance may lead to jobs triggered twice or more if you haven't thought about it :
- when starting instances, you should split the scheduling of existing actions among instances
or
- only 1 webapp instance has a scheduler and schedules actions at regular intervals
or
- you use JDBCJobstore and quartz clustering that should garantee the unique scheduling, but then you may face other "problems" (like having to create quartz tables for each application)
So, I'd really like to see a WOWODC conf about you framework !
Cheers
Alex
Le 31 mars 2011 à 11:19, Philippe Rabier a écrit :
> I'm writing a framework that aims to offer the capability to schedule jobs. It's based on Quartz 2.0 - http://quartz-scheduler.org/
>
> The goals are:
> - persistance is handled by EOF (Quartz offers a JDBC Job store but we use the RAMJobStore instead)
> - a simplified use of Quartz (only one trigger per job for example)
> - no dependency with other frameworks except wonder and EOs that describe a job must implement an interface
>
> We have developed an internally framework but the Quartz library and our business were closely tied. So I extracted the common features. The dev is done and I have to write unit tests before using it in our production env.
>
> It will be free, open.
>
> I will discuss with Pascal if it's worth to show the framework during the WOWODC. Not sure to come but now that I know I won't go to the WWDC (to slow to take my credit card), the choice is simpler.
>
> Philippe
>
> On 31 mars 2011, at 07:34, Gennady Kushnir wrote:
>
>> I use java.util.Timer in my app.
>> It works nice for me sending weekly emails and performing some other actions
>>
>> 2011/3/29 Tim Worman <email@hidden>:
>>> I have used the cron/script approach for a long time and it works quite well. I am starting to transition my apps to use quartz. There's a chance my apps could have multiple deployments and I felt it was necessary to de-couple the app from any outside scripting and schedulers that would also have to be mimic'ed and re-deployed.
>>>
>>> Tim Worman
>>> UCLA GSE&IS
>>>
>>>
>>> On Mar 28, 2011, at 8:10 PM, Matthew Ness wrote:
>>>
>>>>> How would I handle scheduled actions with WebObjects. Cron or some other
>>>>> approach? I'd like to have my application run a daily process to check a
>>>>> remote client's membership status and update my application's membership
>>>>> status.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Ken
>>>>
>>>>
>>>> You could write a simple script which invokes curl, calling a DA in your
>>>> application, and schedule the script as a cron job. You may want to
>>>> include a level of security/authentication in the call.
>>>>
>>>> --
>>>> Matt.
>>>>
>>>> http://logicsquad.net/
>>>>
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list (email@hidden)
>>>> Help/Unsubscribe/Update your Subscription:
>>>>
>>>> This email sent to email@hidden
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden