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

[weston.price@jboss.com]

anonymous wrote : 
  | As far as package/module goes: 
  | 
  | We already discussed this a long time ago. You said you'd move it to the appropriate place. 
  | 

You have an interesting memory :-) What we discussed was the adapter itself. Not where it would end up in CVS, and we most certainly didn't discuss in what version of JBoss it would be released.  I don't mind keeping it in connector, just as long as it's not deployed into AS by default which is where the whole issue came from in the first place. 

anonymous wrote : 
  | ...it does need to be deployed so that the tests can run.
  | 

I see the following in ejb3

org.jboss.ejb3.test.jca.inflowmdb

QuartzMDBean (the listener)
QuartzTest (SLSB remote interface)
QuartzTestBean (the bean itself)

and the following test case:


  |  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());
  |    }
  | 
  |  

Doing a basic validation that a Job was excecuted and the MDB received the message. Is this it, or is there something else in the tutorial or in testsuite? I don't see any Quartz RAR related doc in the EJB3 project or in the EJB tutorial, did I miss something? 













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

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