Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6858

read-resource should return the job file name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • None
    • Batch
    • None

    Description

      The start-job operation must pass the job file name as parameter,

      /deployment=*/subsystem=batch-jberet:read-operation-description(name=start-job)

      however the jon attribute below, returns the job-id name, not the job file name

      /deployment=/subsystem=batch-jberet/job=

      So there is no way to know at runtime, the job file name. Is it possible to return the job xml file name ?

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5320 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.
          • Verified
          is cloned 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

          Activity

            People

              jperkins-rhn James Perkins
              cmiranda@redhat.com Claudio Miranda
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: