Dmn model api still generates DMN 1.1 diagrams in 7.13

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.15.0-alpha3, 7.15.0
    • Affects Version/s: None
    • Component/s: dmn model api
    • None

      Following the example on https://docs.camunda.org/manual/7.13/user-guide/model-api/dmn-model-api/create-a-model/

       

      When I do

       

       

       

       @Test
fun `empty dmn`() {
 val modelInstance = Dmn.createEmptyModel()
 //The next step is to create a DMN definitions element. Set the target namespace on it and add it to the newly created empty model instance.


 val definitions = modelInstance.newInstance(Definitions::class.java)!!
 definitions.namespace = "http://camunda.org/schema/1.0/dmn"
 definitions.name = "definitions";
 definitions.id = "definitions";
 modelInstance.definitions = definitions;

 println(modelInstance.toXml())
}

      The output is

      <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<definitions id="definitions" name="definitions" namespace="http://camunda.org/schema/1.0/dmn" xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd"/>

      But as I am using the 7.13 model API version, I would expect the xmlns to be `xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/"`.

       

      With the current state, I am still able to generate executable dmns, but I cannot create modeler 4.2 compliant dmns when it comes (for example) to layout and informationRequirements.

      Expected: Using the documented code example, I want a modelInstance meta-model that uses DMN 1.3 spec, as the modeler does.

      Note: This might go deeper ... as for example the InformationRequirement class does not define an "id" attribute, which is used to declare and layout decisionTable dependencies.

        1.
        		 Document DMN Model API DMN 1.3 diagram generation Sub-task Closed Nikola Koevski

            Assignee:
            Nikola Koevski
            Reporter:
            Jan Galinski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: