I'd love to have a look at this. Developing code is the ultimate "course" (in the academic sense) in the software being developed.
How exactly would you want it to change? How I understand it something similar to anacron, in that tasks should somehow realize that weren't run and then run one after the other when OpenEJB becomes live? Some thought would have to go into how to keep track of these tasks. But this is the general idea right? Quintin Beukes On Fri, Oct 16, 2009 at 12:22 AM, David Blevins <[email protected]> wrote: > > On Oct 15, 2009, at 2:05 AM, John D. Ament wrote: > >> Well cron style works as well, with an interesting little caveat due to >> the fact that any timers that went off while the app server were down should >> be run when restarted during a failure. I'm working on a project around >> this principal actually, converting a bunch of old perl scripts to something >> a bit more modern. We ended up using a standalone process w/ openejb and >> created a scheduler based on the scripts. It works good, but when I start >> the container all of the jobs kick off, but then resume typical operation. >> >> Ironically, it's exactly what the spec describes to be what should happen. > > Right, we're definitely open to some contributions there if anyone wanted to > take a stab at it. > > We always have an open door policy regardless, but this area in particular > would be a nice spot to dig in. > > -David > >
