[JBoss JIRA] Created: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[JBoss JIRA] Created:...

Wolfgang Laun (JIRA)

Monday, 9 August 2010 Mon, 9 Aug '10

1:47 a.m.

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://jira.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings. -- 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

Wolfgang Laun (JIRA)

Monday, 9 August Mon, 9 Aug

1:55 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://jira.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plugin... ] Wolfgang Laun updated JBRULES-2619: ----------------------------------- Fix Version/s: 5.1.1.FINAL (was: 5.2.0.M1)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://jira.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.1.1.FINAL Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

Edson Tirelli (JIRA)

Friday, 10 September Fri, 10 Sep

9:07 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://jira.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plugin... ] Edson Tirelli updated JBRULES-2619: ----------------------------------- Fix Version/s: 5.2.0.M1 (was: 5.1.1.FINAL)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://jira.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

Mark Proctor (JIRA)

Monday, 16 May Mon, 16 May

10:01 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://issues.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2619: ---------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.M1)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.CR1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Proctor (JIRA)

Tuesday, 17 May Tue, 17 May

4:06 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://issues.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2619: ---------------------------------- Fix Version/s: 5.3.0.M1 (was: 5.2.0.CR1)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.3.0.M1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

6:42 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://issues.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2619: -------------------------------------- Fix Version/s: 5.3.0.CR1 (was: 5.3.0.Beta1)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.3.0.CR1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

3:04 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.3.0.Final Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Proctor (JIRA)

Thursday, 29 September Thu, 29 Sep

2:05 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

[ https://issues.jboss.org/browse/JBRULES-2619?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2619: ---------------------------------- Assignee: Edson Tirelli (was: Mark Proctor)

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.3.0.Final Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

10:02 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.4.0.Beta1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

4:15 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.4.0.Beta2 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

Geoffrey De Smet (JIRA)

Wednesday, 1 February Wed, 1 Feb

4:26 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.4.0.Beta3 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

Toni Rikkola (JIRA)

Thursday, 12 April Thu, 12 Apr

2:37 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

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

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.4.0.Final Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

Toni Rikkola (JIRA)

Tuesday, 15 May Tue, 15 May

7:01 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

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

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.5.0.Beta1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

Michael Anstis (JIRA)

Wednesday, 26 September Wed, 26 Sep

4:28 a.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

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

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 5.5.0.CR1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

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

3:43 p.m.

New subject: [JBoss JIRA] (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes

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

...

Extend API of IF Rule: no access to interesting attributes -------------------------------------------------------------- Key: JBRULES-2619 URL: https://issues.jboss.org/browse/JBRULES-2619 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.FINAL Reporter: Wolfgang Laun Assignee: Edson Tirelli Fix For: 6.0.0.Beta1 Whereas org.drools.rule.Rule contains a wealth of interesting fields, the stable API org.drools.definition.rule.Rule restricts us to getName() and getPackageName() (and some MetaData). I propose an extension of this interface, providing access to agendaGroup, activationGroup and ruleFlowGroup. I see no obvious reason why these user defined attributes should remain hidden. These rule attributes would provide a good opportunity for writing more sophisticated event loggers, letting you specify rule filters by natural rule groupings.

4442

days inactive

5248

days old

jboss-jira@lists.jboss.org

Manage subscription

14 comments

7 participants

tags (0)

participants (7)

Edson Tirelli (JIRA)
Geoffrey De Smet (JIRA)
Geoffrey De Smet (Updated) (JIRA)
Mark Proctor (JIRA)
Michael Anstis (JIRA)
Toni Rikkola (JIRA)
Wolfgang Laun (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBRULES-2619) Extend API of IF Rule: no access to interesting attributes