[
https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi...
]
Gabriele Cardosi commented on DROOLS-3608:
------------------------------------------
[~kkufova]
The last issue you raised here
https://github.com/kiegroup/drools-wb/pull/1091 was
actually due to wrongly written out DMN (I sent you correct one via gchat).
But beside that you explicitly stated that you do not want "partial" solutions
_I don't accept the answer that "top-level collections don't work yet",
as they work with some DMNs_
Probably it was not clear enough, but top-level collection *are* broken; even if you see a
_green_ status after run is only by chance, and it does not mean it actually made the
_right_ comparison you would expect. For example, it turned out that in some cases the DMN
engine turned both input and output to _null_, and then the comparison
"apparently" succeeded.
Last, making only one single PR at the end was exactly what I meant with:
_This mean that I will close this PR and I will create a new one that will include
everything._
Wrong behavior with top level collection in DMN scenario
--------------------------------------------------------
Key: DROOLS-3608
URL:
https://issues.jboss.org/browse/DROOLS-3608
Project: Drools
Issue Type: Sub-task
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Gabriele Cardosi
Priority: Major
Labels: ScenarioSimulation
Attachments: dmn-list.dmn
If you have a DMN file with a top level collection like a list of string not as field of
a complex object but as top level. The type is not correctly loaded and managed.
Top-level collection should work also in Rule scenario.
See dmn-list.dmn as example
--
This message was sent by Atlassian Jira
(v7.12.1#712002)