[JBoss JIRA] Created: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[JBoss JIRA] Created:...

Anatoly Polinsky (JIRA)

Monday, 23 August 2010 Mon, 23 Aug '10

5:29 p.m.

There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group ------------------------------------------------------------------------------------------------- Key: JBRULES-2673 URL: https://jira.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 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Mark Proctor (JIRA)

Wednesday, 18 May Wed, 18 May

5:14 a.m.

New subject: [JBoss JIRA] Commented: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Mark Proctor commented on JBRULES-2673: --------------------------------------- Not sure what you mean, want to provide more details?

...

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 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Proctor (JIRA)

5:14 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2673: ---------------------------------- Comment: was deleted (was: Not sure what you mean, want to provide more details?)

...

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 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Proctor (JIRA)

5:16 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2673: ---------------------------------- Fix Version/s: 5.3.0.M1

...

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.3.0.M1 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Tuesday, 9 August Tue, 9 Aug

1:42 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2673: -------------------------------------- Fix Version/s: 5.3.0.CR1 (was: 5.3.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.3.0.CR1 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Sunday, 25 September Sun, 25 Sep

10:04 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

...

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.3.0.Final 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (Updated) (JIRA)

Friday, 21 October Fri, 21 Oct

5:02 p.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

...

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.Beta1 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (Updated) (JIRA)

Tuesday, 20 December Tue, 20 Dec

11:15 a.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

...

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

Geoffrey De Smet (JIRA)

Wednesday, 1 February Wed, 1 Feb

11:26 a.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

...

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.Beta3 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

Toni Rikkola (JIRA)

Thursday, 12 April Thu, 12 Apr

9:37 a.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2673: ---------------------------------- Fix Version/s: 5.4.0.Final (was: 5.4.0.CR1)

...

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.Final 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

Toni Rikkola (JIRA)

Tuesday, 15 May Tue, 15 May

2:01 p.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2673: ---------------------------------- Fix Version/s: 5.5.0.Beta1 (was: 5.4.0.Final)

...

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.5.0.Beta1 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

Michael Anstis (JIRA)

Wednesday, 26 September Wed, 26 Sep

11:28 a.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2673: ------------------------------------ Fix Version/s: 5.5.0.CR1 (was: 5.5.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.5.0.CR1 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

Michael Anstis (JIRA)

Tuesday, 23 October Tue, 23 Oct

10:43 p.m.

New subject: [JBoss JIRA] (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group

[ https://issues.jboss.org/browse/JBRULES-2673?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2673: ------------------------------------ Fix Version/s: 6.0.0.Beta1 (was: 5.5.0.CR1)

...

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: 6.0.0.Beta1 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

4209

days inactive

5001

days old

jboss-jira@lists.jboss.org

Manage subscription

12 comments

6 participants

tags (0)

participants (6)

Anatoly Polinsky (JIRA)
Geoffrey De Smet (JIRA)
Geoffrey De Smet (Updated) (JIRA)
Mark Proctor (JIRA)
Michael Anstis (JIRA)
Toni Rikkola (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBRULES-2673) There Should be a Relation Between the Fired Rule and the Node which Activates the Ruleflow-Group