Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-227

Support Batch Client Operations in jberet-rest-api

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • None
    • 1.3.0.Beta1
    • jberet-rest-api
    • None

    Description

      • this will help avoid duplicates among jberet-rest-api client;
      • and since these client operations (e.g., starting a job, get job execution, cancel a job execution) access the url defined by server-side resources, it makes sense to keep these client operations along side server resources.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBERET-341 Add stop operation to BatchClient class in jberet-rest-api

          • 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.
          • Resolved
          relates to

          Feature Request - Feature requests from customers and/or users JBERET-149 Support REST API and JAXRS

          • 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.
          • Resolved

          Activity

            People

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: