Thanks for the reply. I was primarily attracted to spring-drools because of the use of Java to define complex logic in the conditions, but I have since found this old thread that summarizes pretty nicely how to do that without spring-drools:<br>
<br><a href="http://article.gmane.org/gmane.comp.java.drools.user/1204">http://article.gmane.org/gmane.comp.java.drools.user/1204</a><br><br>Based on the above suggestion of using "facts" I've come up with the following rule:<br>
<br>rule "Decline Request"<br> dialect "mvel"<br> when<br> request : Request( status == ( RequestStatus.validated ) )<br> Condition( request == request, failed == "true" )<br>
then<br> request.setStatus( requestStatus.declined );<br> update( request );<br>end<br><br>Then I insert into the session Java classes that extend my Condition abstract. Each Condition contains the request, and should any Condition return true from its getFailed method, then the request is declined.<br>
<br>Seem reasonable? <br><br><br><div class="gmail_quote">On Thu, May 29, 2008 at 8:32 AM, Lake Pancake <<a href="mailto:lakepancake@gmail.com">lakepancake@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I found this:<br><br><a href="http://docs.codehaus.org/display/DROOLS/Drools+Spring+Tutorial" target="_blank">http://docs.codehaus.org/display/DROOLS/Drools+Spring+Tutorial</a><br><br>The
latest version available for drools-spring appears to be 2.5-beta-1.
Is it stable and does it work with Drools 4 or should I stay away?<br>
<br>Thanks<br>
</blockquote></div><br>