[Jboss-dev-forums] [Design of JCA on JBoss] - Re: Quartz, timer unification, message inflow RAR

[<wes...@jb...>]

The first pass of this has been added to the connector project under

org.jboss.resource.spi.timer

As well as 

org.jboss.resource.timer

After looking at the working draft (the commonj stuff) there are some differences in the draft and Quartz (this is understandable). Quartz has the concept of a 'job', basically an executable piece of code that gets executed in response to a trigger (basically a timer). The working draft assumes that listeners will respond to timer expiration as well as a set of lifecycle events (ie stop, cancel etc). 

The draft is concerned with timers in the managed scenario where it is assumed that the timer will not execute in a seperate thread, will not be persistent, not have transaction/security contexts etc, etc. 

The mapping of the spi and the underlying implementations EJB3/JMX will have to make up for this discrepancy. This is where we will deviate from the draft. 



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953497#3953497

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953497