-
Bug
-
Resolution: Done
-
Major
-
7.0.2.GA
-
None
META-INF/batch-jobs/batchInJar.xml in a batch jar file inside WAR is ignored and never loaded. This resulted in "javax.batch.operations.JobStartException: JBERET000601: Failed to get job xml file for job batchInJar.xml" when executing a batch job in jar inside WAR.
Here's an example directory structure of the war file and the jar file included in the war file:
[1] batch-jar-in-war.war |-- index.xhtml |-- META-INF | `-- MANIFEST.MF `-- WEB-INF |-- classes | |-- ... | `-- META-INF | `-- batch-jobs | `-- batchInWar.xml <-- This job xml works |-- faces-config.xml |-- lib | `-- simpleBatch-1.0.jar --- [2] `-- web.xml
[2] simpleBatch-1.0.jar |-- META-INF | |-- batch-jobs | | `-- batchInJar.xml <-- This job xml is unable to load |-- processor | `-- ... |-- reader | `-- ... |-- service | `-- ... `-- writer `-- ...
It appears that org.wildfly.extension.batch.jberet.deployment.BatchEnvironmentProcessor and org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver are never invoked for batch jar files under WAR's WEB-INF/lib. And same applies to batch jar files under EAR's lib. Therefore, any job xml in META-INF/batch-jobs is not scanned for such batch jar files.
A same issue was reported in WFLY-4988.
- is cloned by
-
JBEAP-6777 [GSS](7.1.0) Unable to load job xml in jar files inside WAR (and EAR)
- Closed
- is incorporated by
-
JBEAP-8461 [GSS](7.0.z) Upgrade WildFly Core from 2.1.13 to 2.1.14
- Closed
- is related to
-
WFLY-4988 Can't load job from another jar inside ear
- Closed