Re: Scheduled Actions
Re: Scheduled Actions
- Subject: Re: Scheduled Actions
- From: Giles Palmer <email@hidden>
- Date: Thu, 31 Mar 2011 19:17:25 +0100
Hi
This is good timing... At the moment our app sends out event driven notifications but in the not so distant future we need a scheduling mechanism to enhance this.
I have just started to tentatively look at quartz (which seems the way to go). Of course if your framework found itself into Wonder that would be fantastic. I can't make it to WOWODC but any presentation/podcast would be equally welcome!
+1 for github or google code
Giles
> Or, if not github, just stick it on google code (which is subversion) before WOWODC so it is available for people at WOWODC to download it and play with it.
>
> Regards, Kieran
>
> On Mar 31, 2011, at 9:30 AM, Philippe Rabier wrote:
>
>> Kieran, I think about github. I never used so I need to learn the principles but it but it won't be a show stopper.
>>
>> My "dream" would be to include it in Wonder one day to be visible and more used (again if the Wonder committee agrees with).
>>
>> We gain so much time using Wonder that this code could be our contribution in return.
>>
>> The package name is fr.sophiacom.corason.scheduler but I could refactor it a la wonder way.
>>
>> Philippe
>>
>> On 31 mars 2011, at 13:18, Kieran Kelleher wrote:
>>
>>> Showing it at WOWODC is a good idea. Perhaps you can share it on github when it is complete?
>>>
>>> Regards, Kieran
>>>
>>> On Mar 31, 2011, at 5:19 AM, Philippe Rabier wrote:
>>>
>>>> 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
>
> _______________________________________________
> 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