[JBoss JIRA] (JBRULES-3620) Conditional named consequences
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3620?page=com.atlassian.jira.plug... ]
Mario Fusco closed JBRULES-3620.
--------------------------------
Resolution: Done
> Conditional named consequences
> ------------------------------
>
> Key: JBRULES-3620
> URL: https://issues.jboss.org/browse/JBRULES-3620
> Project: JBRULES
> Issue Type: Feature Request
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Implement named consequence like in the following example:
> {{rule R1}}
> {{A() do\[t1\] B()}}
> {{then}}
> {{// default consequence executed with both A() and B()}}
> {{then\[t1\]}}
> {{// named consequence on A()}}
> {{end}}
> In this example, when a match for A() is found, the consequence named t1 is scheduled on the agenda and then the LHS pattern matching evaluation continues as per normal looking for a join with B() and eventually scheduling also the default consequence.
> The named consequence activation can be optionally guarded by a condition like in:
> {{A() if (condition) do\[t1\] B()}}
> Here the named consequence t1 is activated only if the boolean condition (expressed on the last pattern before the if, A() in this case) evaluates to true. The conditional named consequence invocation can be also breaking, i.e. can block any further pattern matching when the condition is satisfied like in:
> {{A() if (condition) break\[t1\] B()}}
> Note that the use of a breaking named consequence without any condition like in:
> {{A() break\[t1\] B()}}
> doesn't make sense (and should generate a compile time error) because the join with B() shouldn't be reachable.
> Using one or more if/else it is also possible to have multiple nested conditions like in the following example:
> {{A() if (condition1) do\[t1\] else if (condition2) do\[t2\] else break\[t3\] B()}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4085) Update subsystem and core-model tests to use WF14
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4085?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-4085:
-------------------------------
Description: I suggest adding a ModelTestControllerVersion.EAP_7_2_0_TMP which is deprecated and pulls in the WF14 artifacts. Once EAP 7.2.0 is out, we need to add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released.
> Update subsystem and core-model tests to use WF14
> -------------------------------------------------
>
> Key: WFCORE-4085
> URL: https://issues.jboss.org/browse/WFCORE-4085
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Kabir Khan
> Assignee: Jeff Mesnil
> Fix For: 7.0.0.Alpha1
>
>
> I suggest adding a ModelTestControllerVersion.EAP_7_2_0_TMP which is deprecated and pulls in the WF14 artifacts. Once EAP 7.2.0 is out, we need to add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4085) Update subsystem and core-model tests to use WF14
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4085?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-4085:
-------------------------------
Description: I suggest adding a ModelTestControllerVersion.EAP_7_2_0_TMP which is deprecated and pulls in the WF14 artifacts. Once EAP 7.2.0 is out, we need to add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder. (was: I suggest adding a ModelTestControllerVersion.EAP_7_2_0_TMP which is deprecated and pulls in the WF14 artifacts. Once EAP 7.2.0 is out, we need to add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released.)
> Update subsystem and core-model tests to use WF14
> -------------------------------------------------
>
> Key: WFCORE-4085
> URL: https://issues.jboss.org/browse/WFCORE-4085
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Kabir Khan
> Assignee: Jeff Mesnil
> Fix For: 7.0.0.Alpha1
>
>
> I suggest adding a ModelTestControllerVersion.EAP_7_2_0_TMP which is deprecated and pulls in the WF14 artifacts. Once EAP 7.2.0 is out, we need to add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months