JBossDeveloper

The idea of this RAR is that it is portable to *ANY Java EE Vendor*.

All this RAR is a simpler User API for using Quartz so that a quartz job can post to an MDB. Nothing more.

Yes, it is bare bones, but it works. And, it is documented somewhat as a EJB3 tutorial.

To be honest, since all you guys have been assholes about this crap, then do whatever the hell you want. I seriously don't care anymore.

As far as package/module goes:

We already discussed this a long time ago. You said you'd move it to the appropriate place.

Move it anywhere, just keep the code around. It doesn't have to be a part of the distro, but it does need to be deployed so that the tests can run.

As far as package/module goes:

We already discussed this a long time ago. You said you'd move it to the appropriate place.

...it does need to be deployed so that the tests can run.

 public void testQuartz() throws Exception
 {
 QuartzTest test = (QuartzTest)InitialContextFactory.getInitialContext().lookup("QuartzTestBean/remote");
 Thread.sleep(5000); // sleep so that quartz mdb runs.
 assertTrue(test.wasCalled());
 }

Moved Quartz RAR to seperate thread.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86667

am i correct in summarizing that the conclusion is we were going to start on our own internal timer SPI ?

i found a reference to http://jira.jboss.com/jira/browse/JBAS-3207 in this topic. the fisheye tab seems to contain references to the initial work by Weston, but yet i don't find this jbosscx directory in HEAD of cvs. am i looking in the right place ?


jbosscx/src/main/org/jboss/resource/spi/timer/CancelTimerListener.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/StopTimerListener.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/Timer.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerData.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerDate.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerDateFormat.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerExcecutionContext.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerException.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerListener.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerManager.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerPeriod.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerProperty.java 1.1 added
jbosscx/src/main/org/jboss/resource/spi/timer/TimerPropertyKey.java 1.1 added
jbosscx/src/main/org/jboss/resource/timer/QuartzSchedulerLoaderAdapter.java 1.1 added
jbosscx/src/main/org/jboss/resource/timer/SchedulerLoaderAdapter.java 1.1 added
jbosscx/src/main/org/jboss/resource/timer/TimerManagerMBean.java 1.1 added
jbosscx/src/main/org/jboss/resource/timer/TimerManagerService.java 1.1 added

here's the main reasons why i opted to revise our own implementation over quartz: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3968946#3968946

note that our own implementation is only targetted at the standard java platform. we have a pluggable interface for async messages and timers. for the enterprise platform, we will be supplying a JMS and EJB Timer based bridges as first priorities.

maybe later if it turns out to be an advantage, we could also build a bridge to the jboss internal timer SPI as it is in the making if i understand correctly.

According to this thread the code moved to the jboss-jca project.

But I don't see it there.

The code in the jboss5 connector project is still the initial check in and hasn't moved
since then.

If nobody is going to work on this further, then I'm going to tag and delete this code.
As it stands it doesn't do anything.

You have a couple of weeks to make me change my mind. ;-)

With the upcoming EJB 3.1 there are new demands on the timer service. These are not addressed by this SPI. I also agree with Tom that Quartz has too many weak spots.