Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9529

Business-central REST API is allowing container creation with empty container id

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 7.47.0.Final
    • Workbench
    • None

      we should not be able to create container with empty containerID but actually if we use business-central REST API then container with empty id is created without any issue.
       
       
      Below REST endpoint is returning success response (201) even when container id is passed as empty in the request body.
       
       

      http://${HOST}:${PORT}/business-central/rest/controller/management/servers/default-kieserver/containers/test

       
       
      Request Body
       

      <container-spec-details>
          <container-id></container-id>
          <container-name>test</container-name>
          <release-id>
              <artifact-id>test</artifact-id>
              <group-id>com.test</group-id>
              <version>1.0.0-SNAPSHOT</version>
          </release-id>
          <configs>
              <entry>
                  <key>RULE</key>
                  <value xsi:type="ruleConfig" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                      <scannerStatus>STOPPED</scannerStatus>
                  </value>
              </entry>
              <entry>
                  <key>PROCESS</key>
                  <value xsi:type="processConfig" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                      <runtimeStrategy>SINGLETON</runtimeStrategy>
                      <kbase></kbase>
                      <ksession></ksession>
                      <mergeMode>MERGE_COLLECTIONS</mergeMode>
                  </value>
              </entry>
          </configs>
          <status>STARTED</status>
      </container-spec-details>

       

              kverlaen@redhat.com Kris Verlaenen
              rhn-support-abhumbe Abhijit Humbe
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: