[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2006) drools integration
[
https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug...
]
Bernd Ruecker commented on JBPM-2006:
-------------------------------------
JSR-94 is not important from my view. Accessing the rule engine are only 10-15 lines of
code. You cannot exchange the rule engine as long as rules aren't exchangable, so I
wouldn't go for JSR-94, nobody uses it in ral projects due to my experience.
For the Drools integration: It is really not hard, but you have a lot of different
possibilities. Like for deployment: Using a serialized rule base or the Guvnor repository?
Condition Evaluation should be decoupled, meaning the rules just create a result which is
evaluated in jbpm (not like the RulesDecisionHandler from Jeff). And so on.
So for me the task would be to define "best practices" how to use Drools in jbpm
and put that into code, but not just do some integration....
drools integration
------------------
Key: JBPM-2006
URL: https://jira.jboss.org/jira/browse/JBPM-2006
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Minor
Fix For: jBPM 4.3
1) deployment:
- deploy rules in source format as part of the business archive
- add a rule deployer to the deployer manager. that will scan for all rules in
sourceformat and compile them into a rulebase. the rulebase & working memory are
deployed objects in the deployment.
2) rules based exclusive condition evaluation
3) decision table activity. maybe this is easier to implement directly instead of using
rules.
Later:
* configurable process variables to submit as facts
* investigate logging integration
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira