[jboss-jira] [JBoss JIRA] (DROOLS-695) Add ability to disable rules

Michael Anstis (JIRA) issues at jboss.org
Wed Jan 21 15:29:49 EST 2015


    [ https://issues.jboss.org/browse/DROOLS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034227#comment-13034227 ] 

Michael Anstis commented on DROOLS-695:
---------------------------------------

The intent would be that the Workbench would have tooling to edit the kmodule.xml with the rules you want to disable/enable.

However it operated yuo'd need to rebuild the KJAR (whether the workbench excludes certain "disabled" rules or whether the kmodule defines what rules to disable at runtime).

Mark has chatted to me about this before. We used to have something called "Build Selectors" in 5.x of the web tooling; which filtered the rules compiled into the deployment unit.

Mark wanted to replace this mechanism with something in kmodule that would filter rules at runtime (as opposed to "build selectors" that worked at compile/author/design time).

> Add ability to disable rules
> ----------------------------
>
>                 Key: DROOLS-695
>                 URL: https://issues.jboss.org/browse/DROOLS-695
>             Project: Drools
>          Issue Type: Enhancement
>    Affects Versions: 6.2.0.CR4
>         Environment: RedHat Linux 6.3 x86_64; Firefox 10.0.5
>            Reporter: Stephen Slaboda
>              Labels: drools-wb
>
> Many times while working on rules, it would be helpful to be able to disable other rules.  Reasons for doing this would be:
> -Testing outside of the workbench (ensure your process using Drools activates certain rules, without the clutter of other rules firing)
> -Turn off rules if it is determined that they are impacitng the operational environment
> -Allow development of rules in the same space while not breaking the build/deploy of rules
> -Allow for inclusion of rules in the operation system that do not run until approved, while still allowing other updates to occur in the meantime.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list