[jboss-jira] [JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFLY-9658:
--------------------------------
    Description: 
In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job.

Visibility should be consistent for starting and querying batch jobs.

More details on https://github.com/jberet/jsr352/issues/105.

  was:
In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job.

Visibility should be consistent for starting and querying batch jobs.



> Batch jobs in a sub-deployment can be started but not queried
> -------------------------------------------------------------
>
>                 Key: WFLY-9658
>                 URL: https://issues.jboss.org/browse/WFLY-9658
>             Project: WildFly
>          Issue Type: Bug
>          Components: Batch
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job.
> Visibility should be consistent for starting and querying batch jobs.
> More details on https://github.com/jberet/jsr352/issues/105.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)