gitgabrio opened a new issue, #2073:
URL: https://github.com/apache/incubator-kie-issues/issues/2073

   Currently, input required for decision evaluation are stored inside the 
DMNContext.
   When further data are required for final decision evaluation (e.g. a 
decision that depends on another decision) then those recursively-needed data 
are stored inside a stack of the context, where each leavel of the stack 
represent a level of the evaluation (to simplify).
   Unfortunately, those additionally evaluated objects are stored only by name, 
and the code currenlty looks for them only at the last level of the stack (if 
present). 
   See
   
[DMNContextImpl.isDefined(String)](https://github.com/apache/incubator-kie-drools/blob/cce41ddce9748bce168275c6505638330ce87076/kie-dmn/kie-dmn-core/src/main/java/org/kie/dmn/core/impl/DMNContextImpl.java#L95)
   [DMNRuntimeImpl.isNodeValueDefined(DMNResultImpl, DMNNode, 
DMNNode)](https://github.com/apache/incubator-kie-drools/blob/cce41ddce9748bce168275c6505638330ce87076/kie-dmn/kie-dmn-core/src/main/java/org/kie/dmn/core/impl/DMNRuntimeImpl.java#L575)
   
   A recent modification in DMN specs, anyway, makes possible to insert an 
input without prefixing it with the name of the model that defines it, and that 
required some workarounds to be implemented.
   
   Those workarounds, in turns, evidentiate the need to review the overall 
structure and logic to see if it is possible to simplify it or better adapt it 
to the new specifications.
   One thing to consider, eventually, is that any level of the stack offer a 
´getNamespace() method´, as in
   
[DMNContextImpl.scopeNamespace()](https://github.com/apache/incubator-kie-drools/blob/cce41ddce9748bce168275c6505638330ce87076/kie-dmn/kie-dmn-core/src/main/java/org/kie/dmn/core/impl/DMNContextImpl.java#L81)
   
   @baldimir @yesamer 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to