]
Geoffrey De Smet updated JBRULES-2673:
--------------------------------------
Fix Version/s: 5.4.0.Beta2
(was: 5.4.0.Beta1)
There Should be a Relation Between the Fired Rule and the Node which
Activates the Ruleflow-Group
-------------------------------------------------------------------------------------------------
Key: JBRULES-2673
URL:
https://issues.jboss.org/browse/JBRULES-2673
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Environment: N/A
Reporter: Anatoly Polinsky
Assignee: Mark Proctor
Labels: drools_flow, ruleflow_group
Fix For: 5.4.0.Beta2
Original Estimate: 1 day
Remaining Estimate: 1 day
We asked for the following behavior to be implemented:
@Test(expected=NameOfOurLayerOtTopOfDroolsException.class)
public void
shouldThrowNameOfOurLayerOtTopOfDroolsExceptionForAnyThrowableThrownWithinDroolsOnTheProcessStart()
{
ksession.startProcess("com.jpmc...process-throws-throwable");
}
@Test(expected=NameOfOurLayerOtTopOfDroolsException.class)
public void
shouldThrowNameOfOurLayerOtTopOfDroolsExceptionForAnyThrowableThrownWithinDroolsOnTheProcessResume()
{
ksession.getWorkItemManager().completeWorkItem( id, null );
}
And Plugtree was prompt to create it for us:
http://anonsvn.jboss.org/repos/labs/labs/jbossrules/branches/5_1_20100802...
The only roadblock here, to fulfill our original request, is when Throwable is thrown
from within a "ruleflow-group" ( from within rules that are embedded into /
invoked from a workflow ), in which case Throwable cannot be caught by the above mechanism
due to the fact that:
"At the moment Drools doesn't keep any relation between the fired rule and the
node which activates the ruleflow-group, thus if an activated rule blows up there is no
way to know which node has made focus on its group"
Since Drools is moving towards having everything under "a single roof/parent of
Knowledge", Process and Rule children should be rather siblings than strangers, hence
should know a little more about each other.
/Anatoly
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: