Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5320

Not possible to start batch job using web console if job id is not same as job XML file name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.DR5
    • 7.0.1.CR2
    • Web Console
    • None

    Description

      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.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBEAP-5650 read-resource should return the job file name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6858 read-resource should return the job file name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. HAL-1161 Not possible to start batch job using web console if job id is not same as job XML file name

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6032 (7.1.0) Upgrade HAL to 2.9.0.Alpha2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              cmiranda@redhat.com Claudio Miranda
              pjelinek@redhat.com Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: