|
From: wolfc <do-...@jb...> - 2006-06-21 13:34:28
|
I'm currently trying to integrate Quartz into the EJB3 stack. I'm taking care that no Quartz classes are needed on the runtime classpath of clients. The API towards the bean container is the EJB Timer Service API as defined in the EJB3 specs, with some helper classes in org.jboss.ejb3.timerservice (like TimerServiceFactory). I also don't want any Quartz classes exposed to a bean developer at compile time. But the extra functionality provided by Quartz should be exposed to bean developers most likely with a JBossTimerService interface which extends javax.ejb.TimerService. I hope this is enough else someone needs to give me requirements of JBoss SPI's. I have no clue what you mean by jarjar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952380#3952380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952380 |