I am working with Quartz 2.1.5 as a Clusterable Scheduler in a Java EE 7 Environment (Wildfly). After a Quartz job is started the job needs to access Java EE session beans. My software is a bit older (no dependency injection was available ) so the job uses jndi lookups to get the session beans. as a jndi lookup I use the 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 am currently fighting the problem that Quartz does not find the Beans using the application scoped jndi name (java:app) It only can find the session bean using the global jndi variant. For some purposes not explained here I need the application scoped variant to work. My Java EE application is all deployed within a single EAR.
Any ideas why only the global JNDI works?
Aucun commentaire:
Enregistrer un commentaire