Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-7945

deploymentBuilder#addXXX(...) should only accept supported resource names

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Duplicate
    • Affects Version/s: 7.7.0
    • Fix Version/s: None
    • Component/s: engine
    • Labels:
      None

      Description

      I had this effect myself when deploying a BpmnModelInstance and also found this on stackoverflow now (https://stackoverflow.com/questions/44518759/camunda-process-definition-deployment-via-api).

      Since deployments for resources that do not have a supported file extension (bpmn, bpmn20.xml, ...) do not work, wouldn't it be a good idea to avoid deployments with unsupported resource-names, or at least log a warning? It can be very nasty to analyse.

      I see these options:

      • check for suffix and raise exception
      • check for suffix and log warning
      • in case of addModelInstance: check for suffix and automatically extend the name based on the model type.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jan.galinski@holisticon.de Jan Galinski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: