[jboss-jira] [JBoss JIRA] Commented: (JBRULES-1020) BRMS Custom Rule Selector for Creating Deployable Packages

Barry Knapp (JIRA) jira-events at lists.jboss.org
Thu Aug 16 06:09:01 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBRULES-1020?page=comments#action_12372484 ] 
            
Barry Knapp commented on JBRULES-1020:
--------------------------------------

> How are the rules marked as "tested" and who sets the effective dates for testing? is it manual?

The rules will be manually updated with "Tested", Effective Date, Expiration Date, Test Effective Date and Test Expiration Date by the business user.  In the long run I would like to automate the tested flag to true when the snapshot containing that rule is deployed to the test environment, but no time for that right now.  :-)
[ Show » ]
Michael Neale [15/Aug/07 10:09 PM] How are the rules marked as "tested" and who sets the effective dates for testing? is it manual?

> have a config file on the classpath that specifies the selectors available. They are a class that implements certain interfaces. Out of the box there
> are none, but if you add one in, then you can choose it in the GUI when you go to build a package (it will show up a list of them, you pick the
> appropriate one) - that allows users to define them in any way they see fit.
> This does NOT however address fields that don't currently exist (like tested dates etc).

This would probably work well for me, since the application will give my class control where I can look up in a custom database table or repository extension for my custom rule properties and values.


> That or we can allow admins to configure a properties file with a fixed list of selectors to choose from - which option sounds better?

The admin configuration of the properties file would be perfect.  The selective deployment script are tightly tied to the rule management process and rule life cycle.  These will be defined one time by IT and probably see little change after that.


> BRMS Custom Rule Selector for Creating Deployable Packages
> ----------------------------------------------------------
>
>                 Key: JBRULES-1020
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1020
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>         Environment: general
>            Reporter: Barry Knapp
>         Assigned To: Michael Neale
>             Fix For: 4.0.1
>
>
> Use Case : Ability to include or exclude rules in a deployable package based on rule meta data or custom rule attributes.
> Add an extension point to the BRMS for deciding which rules should be included in a deployable package.  
> A CustomSelector interface with an boolean accepts(Rule) method would allow implementors to create a class and implement the accepts method.  The custom method could then analyze the rule to determine if the rule should be included in the package being generated by return true for inclusion.  A property file with CustomExtractor=com...implementing class would allow the implementor to inject their CustomSelector class.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       




More information about the jboss-jira mailing list