[jboss-jira] [JBoss JIRA] (WFLY-4988) Can't load job from another jar inside ear

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091881#comment-13091881 ] 

James Perkins commented on WFLY-4988:
-------------------------------------

So the issue is likely that {{dep2.jar}} no longer has access to job XML files in the {{dep1.jar}}. Adding the service {{org.jberet.tools.MetaInfBatchJobsJobXmlResolver}} works because it uses the class path to find batch jobs. Jobs found there will not be manageable from the WildFly console.

The question is should {{dep2.jar}} have knowledge of configuration files in {{dep1.jar}}. I'm not sure where I fall on that. I'd lean towards if you want batch jobs launched from {{dep2.jar}} that's where the job XML files should exist.

> 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)