DMN Elements with null IDs are not correctly managed #1356
Labels
area:dmn
Related to DMN
area:engine
Related to the runtime engines
type:bug
Something is behaving unexpectedly
DMN spec states that the
ID
attribute of anyDMNElements
is OptionalThis is currently not correctly managed in our code base.
The DMNElements are managed in the
DMNModelImpl
inMaps
Those maps are managed with ID as key.
In case of multiple DMNElements of the same kind (eg. Decision Nodes) with no ID, all those nodes will be added in that Map with
null
key, resulting in a collision.We should manage this case using a new key (namespace + name), but I guess we should keep the search by
ID
in place, to preserve the API backword-compatibilityThe text was updated successfully, but these errors were encountered: