[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2006: ------------------------------ Fix Version/s: jBPM 4.0.0.GA (was: jBPM 4.0.0.Beta2) -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2006: ------------------------------ Fix Version/s: jBPM 4.1 (was: jBPM 4.x) Description: 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 was: * rules based exclusive condition evaluation * decision table exclusive activity * configurable process variables to submit as facts * make process variables available as rules global variables * investigate logging integration * investigate joint deployment of rules in process archive Assignee: Joram Barrez -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-2006: ----------------------------------- for number 3) probably its best to create a separate issue. you can decide that when you handle this issue -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Joram Barrez updated JBPM-2006: ------------------------------- Fix Version/s: jBPM 4.2 (was: jBPM 4.1) -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Tom Baeyens reassigned JBPM-2006: --------------------------------- Assignee: Tom Baeyens (was: Joram Barrez) -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-2006: ------------------------------------------- specification: http://www.jcp.org/en/jsr/detail?id=94 Might be useful: http://java.sun.com/developer/technicalArticles/J2SE/JavaRule.html -- 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

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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-2006: ------------------------------------------- Which approach did Jeff Delong follow in jBPM 3.? Did he use serialized rules or a repository? -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2006?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2006. ------------------------------- Resolution: Done -- 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