-
Bug
-
Resolution: Done
-
Blocker
-
7.0.1.CR2
-
None
Using current HAL core master it's not possible to run batch job if job id is not same as job XML file name since console is attempting to use job name instead of job XML file name as 'job-xml-name' attribute when calling start-job operation - see
https://github.com/hal/core/blob/master/gui/src/main/java/org/jboss/as/console/client/shared/subsys/jberet/store/JberetStore.java#L451
https://github.com/hal/core/blob/master/gui/src/main/java/org/jboss/as/console/client/shared/subsys/jberet/ui/JobsRuntimePanel.java#L245
I don't know how console can in current model find out the batch job XML file name.
- is blocked by
-
JBEAP-5650 read-resource should return the job file name
- Verified
- is caused by
-
WFLY-6858 read-resource should return the job file name
- Closed
- is cloned by
-
HAL-1161 Not possible to start batch job using web console if job id is not same as job XML file name
- Resolved
- is incorporated by
-
JBEAP-6032 (7.1.0) Upgrade HAL to 2.9.0.Alpha2
- Closed