[jboss-jira] [JBoss JIRA] (DROOLS-2791) Test DMN Import with 3 layers of antipattern of importing Decision and InputData

[Matteo Mortari (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Mortari updated DROOLS-2791:
-----------------------------------
    Story Points: 2


> Test DMN Import with 3 layers of antipattern of importing Decision and InputData
> --------------------------------------------------------------------------------
>
>                 Key: DROOLS-2791
>                 URL: https://issues.jboss.org/browse/DROOLS-2791
>             Project: Drools
>          Issue Type: Task
>          Components: dmn engine
>            Reporter: Matteo Mortari
>            Assignee: Matteo Mortari
>            Priority: Optional
>         Attachments: image-2018-07-26-16-53-59-141.png, image-2018-07-26-16-54-21-700.png, image-2018-07-26-16-55-16-778.png, image-2018-07-26-16-55-58-807.png
>
>
> Given a "base" model (named _Say hello 1ID1D_, referred as _model A_):
>  !image-2018-07-26-16-53-59-141.png! 
> Given a B model which imports the base decision:
>  !image-2018-07-26-16-54-21-700.png! 
> Given a model B2 which is basically analogous.
> Given a model C which imports model B and model B2, so to form an analogous of a "diamond":
>  !image-2018-07-26-16-55-16-778.png! 
> Atlhought technically not a proper diamond, because Model A is imported both in the scope of Model B, and Model B2, so something like:
>  !image-2018-07-26-16-55-58-807.png! 
> Demonstrate despite antipattern of importing Decision and InputData from imported model, codebase supports the execution.
> [ For completeness: antipattern in the sense is expected from good design/blueprint to actually import BKMs or Decision Service(s), and not really Decisions or InputDatas ]



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)