[jboss-jira] [JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried
Alessandro Moscatelli (JIRA)
issues at jboss.org
Wed May 23 19:35:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581262#comment-13581262 ]
Alessandro Moscatelli commented on WFLY-9658:
---------------------------------------------
Nothing to be sorry about, thank you for your effort
> 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)
More information about the jboss-jira
mailing list