[jboss-jira] [JBoss JIRA] (WFLY-7000) Batch jobs from installed modules should be detected for non-batch app

[James Perkins (JIRA)]

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

James Perkins commented on WFLY-7000:
-------------------------------------

JBeret has an API to allow job XML to be loaded from places other than the {{META-INF/batch-jobs}} directory. Currently during deploy if the deployment does not have a {{META-INF/batch-jobs}} directory the loading of the user services is ignored. The loading of user services, or other module services, should be done regardless of the existence of the batch-jobs directory.

> Batch jobs from installed modules should be detected for non-batch app
> ----------------------------------------------------------------------
>
>                 Key: WFLY-7000
>                 URL: https://issues.jboss.org/browse/WFLY-7000
>             Project: WildFly
>          Issue Type: Bug
>          Components: Batch
>    Affects Versions: 10.0.0.Final
>            Reporter: Mincong Huang
>            Assignee: James Perkins
>
> Hibernate Search is creating a batch job which embedded in a WildFly module. Any user of Hibernate Search should be able to the launch this batch job, no matter if they're using a batch-app. However, it seems that jobs are only resolvable for batch-app. More explicitly, WildFly requires deployed web-app to have the below structure to enable the job resolver:
>     META-INF/batch-jobs
> For those who don't have this batch folder in their webapp, they cannot use the jobs from installed module. And an error "JBERET000601: Failed to get job xml file for job" will be raised.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)