[
https://issues.jboss.org/browse/WFLY-4988?page=com.atlassian.jira.plugin....
]
Ivan Ko commented on WFLY-4988:
-------------------------------
Possibly not 100% related to same issue, but is very similar. Jar inside War file with
batch job.
web.war
WEB-INF
classes
META-INF
batch.xml
lib
client.jar
META-INF
batch.jobs
mybatch.xml
The project structure similar to this works just fine with Wildfly 8.0.0 Final. But
throwing same stack trace when moved to
9.0.0 or 9.0.1 .
This file structure works with newer Wildfly 9
WEB-INF
classes
META-INF
batch.xml
batch-jobs
services
org.jberet.spi.JobXmlResolver as suggested by Daniele.
lib
client.jar
META-INF
batch.jobs
mybatch.xml
It works fine, but not the best solution at the mean time. Is there is any other working
solution for the mean time?
THX
Can't load job from another jar inside ear
------------------------------------------
Key: WFLY-4988
URL:
https://issues.jboss.org/browse/WFLY-4988
Project: WildFly
Issue Type: Bug
Components: Batch
Reporter: Daniele Pirola
Assignee: James Perkins
Prior to 1.1.0.Final I was able to load and start a batch job located in jar 1 from jar
2. Both jars were package inside an ear. Now with the latest introduction of spi resolver
(JobXmlResolverService from wildfly 9) the service created for jar 2 have no
jobXmlResolvers so the start method from JobOperator throws an
javax.batch.operations.JobStartException: JBERET000601: Failed to get job xml file for job
XXX.
According to the spec:
"archive loader If the implementation-specific mechanism does fails to resolve a Job
XML reference, then the batch runtime implementation must resolve the reference with an
archive loader. The implementation must provide an archive loader that resolves the
reference by looking up the reference from the META-INF/batch-jobs directory." I
think that the implementation have to try to load jobs also in META-INF/batch-jobs dir.
Changes in the old behaviour was made due to Issue JBERET-144
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)