[
https://issues.jboss.org/browse/DROOLS-4128?page=com.atlassian.jira.plugi...
]
Edson Tirelli commented on DROOLS-4128:
---------------------------------------
[~manstis] unfortunately, as you've seen, from a spec perspective, the only mandatory
field for importing DMN files is the namespace. We will need to index DMN files if
necessary in the workbench so that we can resolve imports. The presence of locationURI or
any custom attribute we want to add (for instance, we can add a drools:fileName attribute
if it helps), can be used as a shortcut to resolve imports, but can not be relied on. We
need to support imports by namespace.
[DMN Designer] Unable to use a Decision Service that references
imported elements
---------------------------------------------------------------------------------
Key: DROOLS-4128
URL:
https://issues.jboss.org/browse/DROOLS-4128
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.23.0.Final
Reporter: Michael Anstis
Assignee: Guilherme Gomes
Priority: Major
Labels: drools-tools
Attachments: Loan info.dmn, Recommended Loan Products v3 no test case.dmn
The
[
attached|https://issues.jboss.org/secure/attachment/12451671/Recommended%...]
DMN file has a Decision Service ("Whole Model Decision Service") that references
imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not
handle resolution of imported elements in handling of {{DecisionService}} elements.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)