i working quartz 2.1.5 clusterable scheduler in java ee 7 environment (wildfly). after quartz job started job needs access java ee session beans. software bit older (no dependency injection available ) job uses jndi lookups session beans. jndi lookup use portable jndi syntax.
java:app[/module name]/enterprise bean name[/interface name]
or
java:global[/application name]/module name/enterprise bean name[/interface name]
i fighting problem quartz not find beans using application scoped jndi name (java:app) can find session bean using global jndi variant. purposes not explained here need application scoped variant work. java ee application deployed within single ear.
any ideas why global jndi works?
you need implement own org.quartz.spi.threadexecutor and/or org.quartz.spi.threadpool classes make use of javax.enterprise.concurrent package implementation.
the jsr 236: concurrency utilities javatm useful reference.
Comments
Post a Comment