[
https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi...
]
Stylianos Koussouris updated DROOLS-1663:
-----------------------------------------
Workaround Description:
DMNRuntime: it is the same for the whole kcontainer. You create once and reuse for all
your calls.
DMNContext: it is really just a Map<String,Object> of variable values. So you can
pass it in to any call you make. The decisions will check for variables in the context,
and if available, use them.
DMNModel: one per DMN file. Every time you execute a decision service, you need to specify
whick DMNModel should be executed.
So you can create context C, execute DMNModel m1 with context C, then execute DMNModel
m2 with the same context C. The variables will be preserved between calls.
Kie DMN doesn't support IMPORT decisions between DMN files
----------------------------------------------------------
Key: DROOLS-1663
URL:
https://issues.jboss.org/browse/DROOLS-1663
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Stylianos Koussouris
Assignee: Edson Tirelli
DMN Spec 1.1
Page 40.
import: Import [*] This attribute is used to import externally defined elements and
make them available for use by elements in this Definitions.
Section 6.3.3 Import metamodel
The aim here is to be able to import one Decision defined in a separate DMN into another
where it is used as a supporting decision and is referenced (RequiredDecision)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)