-
Bug
-
Resolution: Won't Do
-
Major
-
None
There are 2 EE TCK batch test failures that might have been caused by the fix to WFLY-15921.
com/ibm/jbatch/tck/tests/jslxml/JobOperatorTests.java#testJobOpgetJobInstanceCount_from_ejb
com/ibm/jbatch/tck/tests/jslxml/JobOperatorTests.java#testJobOpgetJobInstanceCount_from_web
So we should apply the same idea to getJobInstances, getJobInstanceCount, getRunningExecutions methods as well, to include jobs that are in the deployment but have not been started.
- clones
-
WFLY-15954 getJobInstances, getJobInstanceCount, getRunningExecutions should include jobs that have not been started
- Closed
- relates to
-
WFLY-15921 JobOperator.getJobNames() does only return Names of Jobs that have already been executed since server start
- Closed