Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
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.
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-11187 Support new DMN 1.3 schema
- Closed