Re: Entirely independent EOF on Quartz Threads - How to do?
Re: Entirely independent EOF on Quartz Threads - How to do?
- Subject: Re: Entirely independent EOF on Quartz Threads - How to do?
- From: Henrique Gomes <email@hidden>
- Date: Thu, 10 May 2012 11:48:04 +0100
Philippe,
Did you manage to get this framework on github?
I was going to 'transplant' some code from a project to a new one where I also need background, scheduled tasks. I thought your code might be a better start pointing.
And if you want to get it integrated in wonder let me know if I can help.
Best regards,
Henrique Gomes
On Feb 17, 2012, at 1:37 PM, Philippe Rabier wrote:
> Hi Paul,
>
> I can give you a complete framework I presented at the last WOWODC that allows Quartz integration in a Wonder app.
> Every class is documented, there is a package-info, … and it allows of course the execution of jobs in // There is also a UI (simple) to see the jobs running and the scheduled jobs.
>
> I have to put on Github, I know and Pascal is ready to help me so it will come…
> It's based on Quartz 2.0. I have to adapt it to Quartz 2.1 (there are some nice enhancements like stop a running job).
>
> So let me know. If you are interested to get the source code, send me an email directly at sophiacom.fr (same user)
>
> Philippe
> @prabier
>
> On 16 févr. 2012, at 23:20, Paul Dunkler wrote:
>
>>> And Wonder have ERCayenne :-)
>>
>> ... i know - Wonder got everything :D I've learned loving it in it's special way. I will take a look at ERCayenne...
>>
>>>> I think it is possible, but not very practical. The last time I looked (long time ago admittedly) you could achieve multithreading, at the expense of throughput (threads waiting on a shared lock).
>>>>
>>>> I'd use Cayenne for this. Seriously ... there's no tie in to the WO UI in case of Quartz headless processor, so it should be much easier switch compared to a webapp. I've done a bunch of Cayenne/Quartz projects for different customers, and parallel execution has never been a problem.
>>
>> I got a mid sized codebase which is highly based on webobjects / wonder and don't have the resources to convert that to a cayenne application. For the first, it would be nice to achieve that with Webobjects/Wonder stuff.
>>
>> And for the other postings - I will take a look at these Background Tasks... thanks
>>
>>>>
>>>> Just my 0.02
>>>>
>>>> Andrus
>>>>
>>>> ---------------
>>>> Andrus Adamchik
>>>> Apache Cayenne ORM: http://cayenne.apache.org/
>>>> Twitter: http://twitter.com/andrus_a
>>>>
>>>>
>>>> On Feb 16, 2012, at 1:29 PM, Paul Dunkler wrote:
>>>>
>>>>> Hi Community,
>>>>>
>>>>> i'm currently working on a WebObjects-Application which uses the Quartz Scheduler to schedule and run thousand but thousand of jobs. Every job is doing some work in the database (Like reading, computing and then Updating/Deleting some Details from the database).
>>>>>
>>>>> This works quite well when i only allow Quartz to start one Single Thread for Job Execution. But when i configure more than one thread, it seams that i have problems with EditingContext / ObjectStoreCoordinator-Locking or something else.
>>>>>
>>>>> The Question is: What should i do to achieve an entirely independent EOF-Stack per Quartz Thread? If it is possible without ramping up a complete EOF-Stack per Thread, this would be even better ;)
>>>>>
>>>>> Currently i just tried to Create a new EditingContext per Job at the start, lock the rootObjectStore, do some things and then unlock the rootObjectStore and dispose the editingContext. But that doesn't seem to work for me.
>>>>>> // Job Start
>>>>>> EOEditingContext anEditingContext = ERXEC.newEditingContext();
>>>>>> anEditingContext.rootObjectStore().lock();
>>>>>
>>>>>> // Job Execution
>>>>>
>>>>>>> // Job End
>>>>>> anEditingContext.saveChanges();
>>>>>> anEditingContext.rootObjectStore().unlock();
>>>>>
>>>>>
>>>>> It would be nice to get your suggestions about this Topic.
>>>>>
>>>>> --
>>>>> Mit freundlichen Grüßen
>>>>>
>>>>> Paul Dunkler
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>> --
>> Mit freundlichen Grüßen / Kind regards
>>
>> Paul Dunkler
>>
>> _______________________________________________
>> 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