[
http://jira.jboss.com/jira/browse/JBRULES-1020?page=comments#action_12372434 ]
Michael Neale commented on JBRULES-1020:
----------------------------------------
One idea on how to do this as an advanced feature:
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).
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