[jboss-jira] [JBoss JIRA] (DROOLS-4911) Allow bound variables to be a function of 3 and 4 other variables

[Lukáš Petrovický (Jira)]

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

Lukáš Petrovický updated DROOLS-4911:
-------------------------------------
    Description: 
For a use case in OptaPlanner's Constraint Streams (see PLANNER-1764), I need to be able to call variable binding functions with 3 and 4 arguments inside accumulate CEs. At the moment, Drools exec model only supports cases of up to 2 arguments. I need to bring the number up to 4.

I do not plan to introduce this functionality into DRL, as my use case leverages exec model directly.



  was:
For a use case in OptaPlanner's Constraint Streams (see PLANNER-1764), I need to be able to call variable binding functions with 3 or 4 arguments. This will allow me to handle cases like this:

{noformat}
$p1: Person()
$p2: Person()
$p3: Person($allMoney: $p1.money + $p2.money + $p3.money)
{noformat}

At the moment, Drools exec model only supports cases of up to 2 arguments. I need to bring the number up to 4.

I do not plan to introduce this functionality into DRL, as my use case leverages exec model directly.





> Allow bound variables to be a function of 3 and 4 other variables
> -----------------------------------------------------------------
>
>                 Key: DROOLS-4911
>                 URL: https://issues.redhat.com/browse/DROOLS-4911
>             Project: Drools
>          Issue Type: Enhancement
>          Components: executable model
>    Affects Versions: 7.31.0.Final
>            Reporter: Lukáš Petrovický
>            Assignee: Lukáš Petrovický
>            Priority: Major
>             Fix For: 7.32.0.Final
>
>
> For a use case in OptaPlanner's Constraint Streams (see PLANNER-1764), I need to be able to call variable binding functions with 3 and 4 arguments inside accumulate CEs. At the moment, Drools exec model only supports cases of up to 2 arguments. I need to bring the number up to 4.
> I do not plan to introduce this functionality into DRL, as my use case leverages exec model directly.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)