Well, i actually thought that you had managed to bind Quartz scheduler to JNDI and that's why i suggested the @Resource approach. But based on your recent reply, it looks like that you are trying to find a way to use the quartz scheduler in your EJB3.
So, is there any specific reason for injecting (or even try to lookup) the scheduler from JNDI? Why not just use the Quartz scheduler APIs to trigger the jobs? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165377#4165377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165377 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
