Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4071

Not able to update kie-server container version using REST API

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4.0
    • 6.3.0.GA
    • Kie-Server
    • None
    • ER2
    • Hide

      1. Check container info:
      [GET] http://localhost:8080/kie-server/services/rest/server/containers/Project1
      =======
      <response type="SUCCESS" msg="Info for container Project1">
      <kie-container container-id="Project1" status="STARTED">
      <messages>
      <content>Container Project1 successfully created with module
      com.example.01652020:Project1:1.0.0.</content>
      <severity>INFO</severity>
      <timestamp>2016-07-04T09:42:00.616+05:30</timestamp>
      </messages>
      <release-id>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.0</version>
      </release-id>
      <resolved-release-id>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.0</version>
      </resolved-release-id>
      <scanner status="DISPOSED" />
      </kie-container>
      </response>
      =======
      2. Update container ID using REST:
      [POST] http://localhost:8080/kie-server/services/rest/server/config/
      =======
      <script>
      <update-release-id container-id="project1">
      <releaseId>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.1</version>
      </releaseId>
      </update-release-id>
      </script>
      =======
      Response:
      ~~~~
      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <responses>
      <response type="SUCCESS" msg="Release id successfully updated.">
      <release-id>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.1</version>
      </release-id>
      </response>
      </responses>
      ~~~~
      3. Restart server instance and check container info:
      [GET] http://localhost:8080/kie-server/services/rest/server/containers/Project1
      =========
      <response type="SUCCESS" msg="Info for container Project1">
      <kie-container container-id="Project1" status="STARTED">
      <messages>
      <content>Container Project1 successfully created with module
      com.example.01652020:Project1:1.0.0.</content>
      <severity>INFO</severity>
      <timestamp>2016-07-04T09:51:25.808+05:30</timestamp>
      </messages>
      <release-id>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.0</version>
      </release-id>
      <resolved-release-id>
      <artifact-id>Project1</artifact-id>
      <group-id>com.example.01652020</group-id>
      <version>1.0.0</version>
      </resolved-release-id>
      <scanner status="DISPOSED" />
      </kie-container>
      </response>
      =========

      Show
      1. Check container info: [GET] http://localhost:8080/kie-server/services/rest/server/containers/Project1 ======= <response type="SUCCESS" msg="Info for container Project1"> <kie-container container-id="Project1" status="STARTED"> <messages> <content>Container Project1 successfully created with module com.example.01652020:Project1:1.0.0.</content> <severity>INFO</severity> <timestamp>2016-07-04T09:42:00.616+05:30</timestamp> </messages> <release-id> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.0</version> </release-id> <resolved-release-id> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.0</version> </resolved-release-id> <scanner status="DISPOSED" /> </kie-container> </response> ======= 2. Update container ID using REST: [POST] http://localhost:8080/kie-server/services/rest/server/config/ ======= <script> <update-release-id container-id="project1"> <releaseId> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.1</version> </releaseId> </update-release-id> </script> ======= Response: ~~~~ <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <responses> <response type="SUCCESS" msg="Release id successfully updated."> <release-id> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.1</version> </release-id> </response> </responses> ~~~~ 3. Restart server instance and check container info: [GET] http://localhost:8080/kie-server/services/rest/server/containers/Project1 ========= <response type="SUCCESS" msg="Info for container Project1"> <kie-container container-id="Project1" status="STARTED"> <messages> <content>Container Project1 successfully created with module com.example.01652020:Project1:1.0.0.</content> <severity>INFO</severity> <timestamp>2016-07-04T09:51:25.808+05:30</timestamp> </messages> <release-id> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.0</version> </release-id> <resolved-release-id> <artifact-id>Project1</artifact-id> <group-id>com.example.01652020</group-id> <version>1.0.0</version> </resolved-release-id> <scanner status="DISPOSED" /> </kie-container> </response> =========

    Description

      I updated a kie-container's release Id using "UpdateReleaseIdCommand". It worked fine, but after the server restart it's going back to the old release Id's version.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHBPMS-4072 [GSS] (6.3.z)Not able to update kie-server container version using REAT 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.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-1224 Not able to update kie-server container version using 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.
          • Closed

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              rhn-support-abhumbe Abhijit Humbe
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: