From: <jbo...@li...> - 2006-03-19 05:54:03
|
Author: mar...@jb... Date: 2006-03-19 00:54:00 -0500 (Sun, 19 Mar 2006) New Revision: 3031 Modified: trunk/labs/jbossrules/documentation/manual/Part - 1/Chapter - Rule Engine/Section - What is a Rule Engine.xml Log: -Added a brief mention of Agendas Modified: trunk/labs/jbossrules/documentation/manual/Part - 1/Chapter - Rule Engine/Section - What is a Rule Engine.xml =================================================================== --- trunk/labs/jbossrules/documentation/manual/Part - 1/Chapter - Rule Engine/Section - What is a Rule Engine.xml 2006-03-19 05:46:15 UTC (rev 3030) +++ trunk/labs/jbossrules/documentation/manual/Part - 1/Chapter - Rule Engine/Section - What is a Rule Engine.xml 2006-03-19 05:54:00 UTC (rev 3031) @@ -113,6 +113,14 @@ <para>When we get the Query Results the List has a size of two and references "cheddar" and "mozarella", as expected. If we had used a Rule - constructed instead of a Query the Terminal Node's Consequence would have + construct instead of a Query the Terminal Node's Consequence would have attempted to fire twice, once for "cheddar" and once for "mozarella".</para> + + <para>When a Rule is Fully Matched it does not fire immediately. Instead the + Rule plus the matched Facts are <indexterm> + <primary>Activated</primary> + </indexterm> placed onto the <indexterm> + <primary>Agenda</primary> + </indexterm>; which is responsible for the scheduling and firing + Activations.</para> </section> \ No newline at end of file |