On 2010-11-26 18.39, Paul Merlin wrote:
I worked on Quartz Scheduler integration during Devoxx and got headaches.
On one side using composites as jobs for a volatile scheduler is working nicely
but on the other side writing a JobStore that use a Qi4j EntityStore is a
tedious task.
In Quartz the only interesting implementation is in JobStoreSupport
(http://www.docjar.com/html/api/org/quartz/impl/jdbcjobstore/JobStoreSupport.java.html).
It's a _big_ class, mixing SQL concepts, denormalized schema of the Quartz
database and business rules. IMNSHO a big ball of mud. The only implementation
that could give us some light is the terracota one but sadly it's not
opensource.
Should I push the volatile version for now ?
Ok, that sucks... hm... I don't particularly like the idea of
reinventing this wheel, but if their API is too screwed up then maybe
that's the best way to do it, with a fair share of "inspiration" going on.
What would be easiest: from scratch, or continue with JobStoreSupport?
Got gut feeling?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
