From: <jbo...@li...> - 2006-04-20 05:09:26
|
Author: mic...@jb... Date: 2006-04-20 01:09:19 -0400 (Thu, 20 Apr 2006) New Revision: 3837 Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml Log: Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml =================================================================== --- labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml 2006-04-20 04:07:27 UTC (rev 3836) +++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml 2006-04-20 05:09:19 UTC (rev 3837) @@ -47,4 +47,20 @@ <para>Tool Integration</para> </listitem> </itemizedlist> + + <section> + <title>When not to use a rule engine</title> + <para> + To quote a Drools mailing list regular (Dave Hamu): + "It seems to me that in the excitement of working +with rules engines, that people forget that a rules engine is only one +piece of a complex application or solution. Rules engines are not +really intended to handle workflow or process executions nor are +workflow engines or process management tools designed to do rules. Use +the right tool for the job. Sure, a pair of pliers can be used as a +hammering tool in a pinch, but that's not what it's designed for." + + </para> + </section> + </section> \ No newline at end of file |