Wednesday, December 05, 2007

Rule Constraints and Code Constraints now works for Splits

Recently I got the Drools dialect system working for processes, as discussed in this previous blog article. The dialect system is a pluggable framework to allow code to be written with different languages. Previously Split constraints would only work with rules, so the next stage was naturally to allow for constraints to work with code, like traditional process engines - ofcourse the code constraint would also work with the dialect system. Below is a screenshot of a Split node with both MVEL and Java code constraints and MVEL and Java rule constraints.



  1. Hi,

    I was wondering is there anywhere in the drools roadmap a view for supporting java 1.6.
    I couldn't find any specific drools forum to ask the question there.

    Thanks in advance

  2. There is a user mailing list. Most things work with java1.6, except the dynamic function reloading. We will try and address that for the next release.