[jboss-svn-commits] JBL Code SVN: r34186 - in labs/jbossrules/trunk/drools-docs: drools-docs-expert/src/main/docbook/en-US/Chapter-Examples and 9 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Jul 26 09:17:43 EDT 2010
Author: ge0ffrey
Date: 2010-07-26 09:17:41 -0400 (Mon, 26 Jul 2010)
New Revision: 34186
Modified:
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Templates.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SudokuExample.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-DSL.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-Rule.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-TypeDeclaration.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Performance_Tuning/Section-Performance.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Quick_Start/Section-More_On_Building_And_Deploying.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-DSL.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-Rule.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-TypeDeclaration.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-User_Guide/Section-Running.xml
labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Flow/Chapter-RuleFlow.xml
labs/jbossrules/trunk/drools-docs/drools-docs-integration/src/main/docbook/en-US/Chapter-Server/Section-Configuration/Section-Configuration.xml
labs/jbossrules/trunk/drools-docs/drools-docs-introduction/src/main/docbook/en-US/Chapter-Install/Section-Maven_build.xml
Log:
don't use <programlisting> inside <para> (gives code coloring issues)
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Templates.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Templates.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Templates.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -99,8 +99,7 @@
<para>An important parameter is available without having to be
included in the data source providing the actual values. The
parameter substitution
- <programlisting>
-<emphasis role="bold">@{row.rowNumber}</emphasis></programlisting>
+ <emphasis role="bold"><code>@{row.rowNumber}</code></emphasis>
expands to the integers 0, 1, 2, etc., providing a unique distinction
for the instantiation derived from a parameter set. You would use this
as part of each rule name, because, without this precaution, there
@@ -126,13 +125,13 @@
<para>You may use a Java object that provides getter methods
corresponding to all of the parameter names of your template
- file. If, for instance, you have defined a header
+ file. If, for instance, you have defined a header</para>
<programlisting>
template header
type
limit
word</programlisting>
- the following Java class could be used:
+ <para>the following Java class could be used:</para>
<programlisting role="JAVA">
public class ParamSet {
//...
@@ -143,7 +142,7 @@
public int getLimit(){...}
public boolean isWord(){...}
}</programlisting>
- Although interpolation is pure text manipulation, the actual values
+ <para>Although interpolation is pure text manipulation, the actual values
supplied may be of any type, just as long as this type provides a
reasonable <code>toString()</code> method. (For simple types, the
eponymous static method of the related class from <code>java.lang</code>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SudokuExample.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SudokuExample.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SudokuExample.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -139,7 +139,8 @@
</screenshot></para>
<para>In addition, the validation rule set outputs all of the issues
- which are discovered to the console. <programlisting>
+ which are discovered to the console.</para>
+ <programlisting>
There are two cells on the same column with the same value at (6,0) and (4,0)
There are two cells on the same column with the same value at (4,0) and (6,0)
There are two cells on the same row with the same value at (2,4) and (2,2)
@@ -155,7 +156,7 @@
There are two cells in the same zone with the same value at (6,3) and (7,3)
There are two cells in the same zone with the same value at (7,3) and (6,3)
There are two cells on the same column with the same value at (7,3) and (6,3)
-There are two cells on the same column with the same value at (6,3) and (7,3)</programlisting></para>
+There are two cells on the same column with the same value at (6,3) and (7,3)</programlisting>
<para>We will look at the solving rule set later in this section, but
for the moment we should note that some theoretically solvable solutions
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-DSL.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-DSL.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-DSL.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -176,13 +176,16 @@
is to make things as fluent as possible.</para>
<para>To use the DSL when you want to compile and run the rules, you will
- need to pass the DSL configuration source along with the rule source.
+ need to pass the DSL configuration source along with the rule source.</para>
<programlisting>PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( source, dsl );
//source is a reader for the rule source, dsl is a reader for the DSL configuration
-</programlisting> You will also need to specify the expander by name in the
- rule source file: <programlisting>expander your-expander.dsl
-</programlisting>Typically you keep the DSL in the same directory as the rule,
+</programlisting>
+ <para>You will also need to specify the expander by name in the
+ rule source file:</para>
+ <programlisting>expander your-expander.dsl
+</programlisting>
+ <para>Typically you keep the DSL in the same directory as the rule,
but this is not required if you are using the above API (you only need to
pass a reader). Otherwise everything is just the same.</para>
@@ -222,15 +225,16 @@
<para>This is easier to explain with an example. Lets take look at Cheese
class, with the following fields: type, price, age, country. We can
- express some LHS condition in normal DRL like the following
+ express some LHS condition in normal DRL like the following</para>
<programlisting>Cheese(age < 5, price == 20, type=="stilton", country=="ch")</programlisting>
- If you know ahead of time that you will use all the fields, all the time,
+ <para>If you know ahead of time that you will use all the fields, all the time,
it is easy to do a mapping using the above techniques. However, chances
are that you will have many fields, and many combinations. If this is the
- case, you can setup your mappings like so: <programlisting>[when]There is a Cheese with=Cheese()
+ case, you can setup your mappings like so:</para>
+ <programlisting>[when]There is a Cheese with=Cheese()
[when]- age is less than {age}=age<{age}
[when]- type is '{type}'=type=='{type}'
-[when]- country equal to '{country}'=country=='{country}'</programlisting></para>
+[when]- country equal to '{country}'=country=='{country}'</programlisting>
<para><emphasis role="bold">IMPORTANT:</emphasis> It is NOT possible to
use the "-" feature after an <emphasis role="bold">accumulate</emphasis>
@@ -268,21 +272,25 @@
used by any attribute. NOTE: The order of the entries in the DSL is
important. </para>
- <para><programlisting>[when][]is less than or equal to=<=
+ <programlisting>[when][]is less than or equal to=<=
[when][]is less than=<
[when][]is greater than or equal to=>=
[when][]is greater than=>
[when][]is equal to===
[when][]equals===
[when][]- {field:\w*} {operator} {value:\d*}={field} {operator} {value}
-[when]There is a Cheese with=Cheese()</programlisting> Now, you can then write
- rules with conditions like the following: <programlisting>There is a Cheese with
+[when]There is a Cheese with=Cheese()</programlisting>
+ <para>Now, you can then write
+ rules with conditions like the following:</para>
+ <programlisting>There is a Cheese with
- age is less than 42
- rating is greater than 50
- - type equals 'stilton'</programlisting> The parser will pick up the
+ - type equals 'stilton'</programlisting>
+ <para>The parser will pick up the
"-" lines (they have to be on their own line) and add them as constraints
to the declaration above. So in this specific case, using the above
- mappings, is the equivalent to doing (in DRL): <programlisting>Cheese(age<42, rating > 50, type=='stilton')</programlisting></para>
+ mappings, is the equivalent to doing (in DRL):</para>
+ <programlisting>Cheese(age<42, rating > 50, type=='stilton')</programlisting>
</section>
<section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-Rule.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-Rule.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-Rule.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -1524,27 +1524,27 @@
<para>Here is a simple example of reasoning and binding on another
pattern sub-field:</para>
- <para><programlisting>rule "validate zipcode"
+ <programlisting>rule "validate zipcode"
when
Person( $personAddress : address )
Address( zipcode == "23920W") from $personAddress
then
# zip code is ok
end
-</programlisting></para>
+</programlisting>
<para>With all the flexibility from the new expressiveness in the Drools
engine you can slice and dice this problem many ways. This is the same
but shows how you can use a graph notation with the 'from':</para>
- <para><programlisting>rule "validate zipcode"
+ <programlisting>rule "validate zipcode"
when
$p : Person( )
$a : Address( zipcode == "23920W") from $p.address
then
# zip code is ok
end
-</programlisting></para>
+</programlisting>
<para>Previous examples were evaluations using a single pattern. The
CE <literal>from</literal> also support object sources that return a collection of objects.
@@ -1571,7 +1571,7 @@
as it may produce unexpected results. Consider the example provided earlier, but
now slightly modified as follows:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1590,10 +1590,10 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>
- In the above example, persons in Raleigh, NC should be assigned to sales region 1 and
+ In the above example, persons in Raleigh, NC should be assigned to sales region 1 and
receive a discount; i.e., you would expect both rules to activate and fire. Instead you
will find that only the second rule fires.</para>
@@ -1638,7 +1638,7 @@
because the graph is fairly simple, an even easier solution is to modify your
rules as follows:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1655,7 +1655,7 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>Now, you will find that both rules fire as expected. However, it is not
always possible to access nested facts as above. Consider an example where a Person
@@ -1670,7 +1670,7 @@
For example, the following use of <literal>from</literal> causes both rules to fire as
expected:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1689,11 +1689,11 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>However, the following slightly different approach does exhibit the problem:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1715,7 +1715,7 @@
exists (Address( city == "Raleigh") from $addresses)
then
modify ($assessment) {} #Modify assessment in a modify block
-end</programlisting></para>
+end</programlisting>
<para>In the above example, the $addresses variable is returned from the
use of <literal>from</literal>. The example also introduces
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-TypeDeclaration.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-TypeDeclaration.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Language_Reference/Section-TypeDeclaration.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -162,8 +162,8 @@
Drools: fact types, fact attributes and rules. Drools uses the
at sign ('@') to introduce metadata, and it always uses the form:</para>
- <para><programlisting>@<emphasis>metadata_key</emphasis>( <emphasis>metadata_value</emphasis> )</programlisting>The
- parenthesized <emphasis>metadata_value</emphasis> is optional.</para>
+ <programlisting>@<emphasis>metadata_key</emphasis>( <emphasis>metadata_value</emphasis> )</programlisting>
+ <para>The parenthesized <emphasis>metadata_value</emphasis> is optional.</para>
<para>For instance, if you want to declare a metadata attribute like
<code>author</code>, whose value is <emphasis>Bob</emphasis>, you
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Performance_Tuning/Section-Performance.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Performance_Tuning/Section-Performance.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Performance_Tuning/Section-Performance.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -93,14 +93,15 @@
situations where a user has a limited amount of memory or for some reason
does not want to incur in the indexing overhead, indexing can be disabled
for each of the memories, by setting the following system properties to
- false: <programlisting>org.drools.reteoo.beta.index-left
+ <literal>false</literal>:</para>
+ <programlisting>org.drools.reteoo.beta.index-left
org.drools.reteoo.beta.index-right
For example:
..when you launch the application (or in the container as appropriate).
-Dorg.drools.reteoo.beta.index-right=false
-Dorg.drools.reteoo.beta.index-left=false
-</programlisting></para>
+</programlisting>
</section>
<section>
@@ -123,8 +124,9 @@
lets use Manners 64 benchmark test results on a Pentium IV 3 Ghz HT
machine with 1.0 Gb memory. This is not really a detailed benchmark test,
but simply some rough numbers in order to make the scenario easier to
- understand: <programlisting>Manners 64 without indexes: 135000 millisec to run
-Manners 64 with BetaNode indexes: 10078 millisec to run on average</programlisting></para>
+ understand:</para>
+ <programlisting>Manners 64 without indexes: 135000 millisec to run
+Manners 64 with BetaNode indexes: 10078 millisec to run on average</programlisting>
<para>It is obvious by the previous run times that indexes overall
benefits pays off the overhead to keep them, at least in terms of
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Quick_Start/Section-More_On_Building_And_Deploying.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Quick_Start/Section-More_On_Building_And_Deploying.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Quick_Start/Section-More_On_Building_And_Deploying.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -102,11 +102,11 @@
KnowledgeAgentConfiguration object passed to the agent.
</para>
- <para>For polling to occur, the polling and notifier services must be started:
+ <para>For polling to occur, the polling and notifier services must be started:</para>
<programlisting role="JAVA">ResourceFactory.getResourceChangeNotifierService().start();
ResourceFactory.getResourceChangeScannerService().start();</programlisting>
- </para>
+
<section>
<title>Knowledge Agent and Custom ClassLoaders</title>
<para>Because Knowledge Agent could scan and process remote resources, it
@@ -174,11 +174,11 @@
<para>
The following code snippet creates a new Knowledge Agent with its
"newInstace" property set to false
+ </para>
<programlisting role="JAVA">KnowledgeAgentConfiguration aconf = KnowledgeAgentFactory.newKnowledgeAgentConfiguration();
aconf.setProperty("drools.agent.newInstance", "false");
KnowledgeAgent kagent = KnowledgeAgentFactory.newKnowledgeAgent("test agent", null, aconf);
</programlisting>
- </para>
</section>
<section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -924,8 +924,8 @@
<para>To use a filter specify it while calling <code>FireAllRules</code>. The
following example permits only rules ending in the string <emphasis>Test</emphasis>.
- All others will be filtered out.
- <programlisting role="JAVA">workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );</programlisting></para>
+ All others will be filtered out.</para>
+ <programlisting role="JAVA">workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );</programlisting>
</section>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-DSL.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-DSL.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-DSL.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -172,13 +172,16 @@
is to make things as fluent as possible.</para>
<para>To use the DSL when you want to compile and run the rules, you will
- need to pass the DSL configuration source along with the rule source.
+ need to pass the DSL configuration source along with the rule source.</para>
<programlisting>PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( source, dsl );
//source is a reader for the rule source, dsl is a reader for the DSL configuration
-</programlisting> You will also need to specify the expander by name in the
- rule source file: <programlisting>expander your-expander.dsl
-</programlisting>Typically you keep the DSL in the same directory as the rule,
+</programlisting>
+ <para>You will also need to specify the expander by name in the
+ rule source file:</para>
+ <programlisting>expander your-expander.dsl
+</programlisting>
+ <para>Typically you keep the DSL in the same directory as the rule,
but this is not required if you are using the above API (you only need to
pass a reader). Otherwise everything is just the same.</para>
@@ -217,15 +220,16 @@
<para>This is easier to explain with an example. Lets take look at Cheese
class, with the following fields: type, price, age, country. We can
- express some LHS condition in normal DRL like the following
+ express some LHS condition in normal DRL like the following</para>
<programlisting>Cheese(age < 5, price == 20, type=="stilton", country=="ch")</programlisting>
- If you know ahead of time that you will use all the fields, all the time,
+ <para>If you know ahead of time that you will use all the fields, all the time,
it is easy to do a mapping using the above techniques. However, chances
are that you will have many fields, and many combinations. If this is the
- case, you can setup your mappings like so: <programlisting>[when]There is a Cheese with=Cheese()
+ case, you can setup your mappings like so:</para>
+ <programlisting>[when]There is a Cheese with=Cheese()
[when]- age is less than {age}=age<{age}
[when]- type is '{type}'=type=='{type}'
-[when]- country equal to '{country}'=country=='{country}'</programlisting></para>
+[when]- country equal to '{country}'=country=='{country}'</programlisting>
<para><emphasis role="bold">IMPORTANT:</emphasis> It is NOT possible to
use the "-" feature after an <emphasis role="bold">accumulate</emphasis>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-Rule.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-Rule.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-Rule.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -1460,27 +1460,27 @@
<para>Here is a simple example of reasoning and binding on another
pattern sub-field:</para>
- <para><programlisting>rule "validate zipcode"
+ <programlisting>rule "validate zipcode"
when
Person( $personAddress : address )
Address( zipcode == "23920W") from $personAddress
then
# zip code is ok
end
-</programlisting></para>
+</programlisting>
<para>With all the flexibility from the new expressiveness in the Drools
engine you can slice and dice this problem many ways. This is the same
but shows how you can use a graph notation with the 'from':</para>
- <para><programlisting>rule "validate zipcode"
+ <programlisting>rule "validate zipcode"
when
$p : Person( )
$a : Address( zipcode == "23920W") from $p.address
then
# zip code is ok
end
-</programlisting></para>
+</programlisting>
<para>Previous examples were reasoning over a single pattern. The
<emphasis role="bold">from</emphasis> CE also support object sources
@@ -1508,7 +1508,7 @@
as it may produce unexpected results. Consider the example provided earlier, but
now slightly modified as follows:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1527,7 +1527,7 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>
In the above example, persons in Raleigh, NC should be assigned to sales region 1 and
@@ -1575,7 +1575,7 @@
the graph is fairly simple, an even easier solution is to modify your rules as follows:
</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1592,7 +1592,7 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>Now, you will find that both rules fire as expected. However, it is not
always possible to access nested facts as above. Consider an example where a Person
@@ -1608,7 +1608,7 @@
the following use of <emphasis role="bold">from</emphasis> causes both rules to fire as expected:
</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1627,11 +1627,11 @@
then
modify ($p) {} #Apply discount to person in a modify block
end
-</programlisting></para>
+</programlisting>
<para>However, the following slightly different approach does exhibit the problem:</para>
- <para><programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
+ <programlisting>rule "Assign people in North Carolina (NC) to sales region 1"
ruleflow-group "test"
lock-on-active true
when
@@ -1653,7 +1653,7 @@
exists (Address( city == "Raleigh") from $addresses)
then
modify ($assessment) {} #Modify assessment in a modify block
-end</programlisting></para>
+end</programlisting>
<para>In the above example, the $addresses variable is returned from the
use of <emphasis role="bold">from</emphasis>. The example also introduces
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-TypeDeclaration.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-TypeDeclaration.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Language/Section-TypeDeclaration.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -146,8 +146,9 @@
<emphasis role="bold">@</emphasis> symbol to introduce metadata, and it
always uses the form:</para>
- <para><programlisting>@matadata_key( metadata_value )</programlisting>The
- parenthesis and the metadata_value are optional.</para>
+ <programlisting>@matadata_key( metadata_value )</programlisting>
+
+ <para>The parenthesis and the metadata_value are optional.</para>
<para>For instance, if you want to declare a metadata attribute like
<emphasis>author</emphasis>, whose value is <emphasis>Bob</emphasis>, you
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-User_Guide/Section-Running.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-User_Guide/Section-Running.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-User_Guide/Section-Running.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -335,7 +335,8 @@
<para>To use a filter specify it while calling
<code>fireAllRules()</code>. The following example permits only rules
ending in the string <code>"Test"</code>. All others will be filtered
- out. <programlisting role="JAVA">ksession.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );</programlisting></para>
+ out.</para>
+ <programlisting role="JAVA">ksession.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );</programlisting>
</section>
</section>
</section>
@@ -460,7 +461,7 @@
this group. It is also always the first group on the stack, given focus
initially, by default.</para>
- <para><programlisting role="JAVA">ksession.getAgenda().getAgendaGroup( "Group A" ).setFocus();</programlisting></para>
+ <programlisting role="JAVA">ksession.getAgenda().getAgendaGroup( "Group A" ).setFocus();</programlisting>
</section>
<section>
@@ -481,8 +482,8 @@
"activation-group" rule attribute. In this group only one rule can fire,
and after that rule has fired all the other rules are cancelled from the
agenda. The <code>clear()</code> method can be called at any time, which
- cancels all of the activations before one has had a chance to fire.
- <programlisting role="JAVA">ksession.getAgenda().getActivationGroup( "Group B" ).clear();</programlisting></para>
+ cancels all of the activations before one has had a chance to fire.</para>
+ <programlisting role="JAVA">ksession.getAgenda().getActivationGroup( "Group B" ).clear();</programlisting>
</section>
<section>
@@ -504,8 +505,8 @@
group is activate. The group itself can only become active when the
elaboration of the ruleflow diagram reaches the node representing the
group. Here too, the <code>clear()</code> method can be called at any
- time to cancels all activations still remaining on the Agenda.
- <programlisting role="JAVA">ksession.getAgenda().getRuleFlowGroup( "Group C" ).clear();</programlisting></para>
+ time to cancels all activations still remaining on the Agenda.</para>
+ <programlisting role="JAVA">ksession.getAgenda().getRuleFlowGroup( "Group C" ).clear();</programlisting>
</section>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Flow/Chapter-RuleFlow.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Flow/Chapter-RuleFlow.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Flow/Chapter-RuleFlow.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -154,8 +154,8 @@
<section>
<title>Example 1</title>
- <para>This is a simple example of a basic process with a ruleset node only:
- <programlisting role="JAVA">
+ <para>This is a simple example of a basic process with a ruleset node only:</para>
+ <programlisting role="JAVA">
RuleFlowProcessFactory factory =
RuleFlowProcessFactory.createProcess("org.drools.HelloWorldRuleSet");
factory
@@ -173,7 +173,6 @@
.connection(1, 2)
.connection(2, 3);
RuleFlowProcess process = factory.validate().getProcess();</programlisting>
- </para>
<para>You can see that we start by calling the static <code>createProcess()</code>
method from the <code>RuleFlowProcessFactory</code> class. This method creates
@@ -209,7 +208,7 @@
<section>
<title>Example 2</title>
- <para>This example is using Split and Join nodes:
+ <para>This example is using Split and Join nodes:</para>
<programlisting role="JAVA">
RuleFlowProcessFactory factory =
RuleFlowProcessFactory.createProcess("org.drools.HelloWorldJoinSplit");
@@ -235,7 +234,6 @@
.connection(4, 5)
.connection(5, 6);
RuleFlowProcess process = factory.validate().getProcess();</programlisting>
- </para>
<para>This shows a simple example using Split and Join nodes. As you can see,
a Split node can have multiple outgoing connections, and a Join node multiple
@@ -248,8 +246,8 @@
<section>
<title>Example 3</title>
- <para>Now we show a more complex example with a ForEach node, where we have nested nodes:
- <programlisting role="JAVA">
+ <para>Now we show a more complex example with a ForEach node, where we have nested nodes:</para>
+ <programlisting role="JAVA">
RuleFlowProcessFactory factory =
RuleFlowProcessFactory.createProcess("org.drools.HelloWorldForeach");
factory
@@ -278,7 +276,6 @@
.connection(1, 2)
.connection(2, 5);
RuleFlowProcess process = factory.validate().getProcess();</programlisting>
- </para>
<para>Here you can see how we can include a ForEach node with nested action nodes.
Note the <code>linkIncomingConnections()</code> and
@@ -355,10 +352,10 @@
are then copied to the newly created process instance as top-level variables
of the process.</para>
- <para>You can also start a process from within a rule consequence, using
+ <para>You can also start a process from within a rule consequence, using</para>
<programlisting role="JAVA">
kcontext.getKnowledgeRuntime().startProcess("com.sample.MyProcess");</programlisting>
- </para></listitem>
+ </listitem>
</orderedlist>
@@ -1395,9 +1392,9 @@
to respond to the given fault. In most cases, the behavior that is
needed to react to the given fault cannot be expressed in one action.
It is therefore recommended to have the exception handler signal an
- event of a specific type (in this case "Fault") using <programlisting role="JAVA">
+ event of a specific type (in this case "Fault") using</para>
+ <programlisting role="JAVA">
context.getProcessInstance().signalEvent("FaultType", context.getVariable("FaultVariable");</programlisting>
- </para>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-integration/src/main/docbook/en-US/Chapter-Server/Section-Configuration/Section-Configuration.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-integration/src/main/docbook/en-US/Chapter-Server/Section-Configuration/Section-Configuration.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-integration/src/main/docbook/en-US/Chapter-Server/Section-Configuration/Section-Configuration.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -115,8 +115,9 @@
classloader.</para>
<para>If you want to deploy in a AS5 you simply must add this bean
- definition line.<programlisting><bean id="jbossResolver" class="org.apache.camel.jboss.JBossPackageScanClassResolver"/></programlisting>Another
- important configuration is the Camel Context declaration, as you can
+ definition line.</para>
+ <programlisting><bean id="jbossResolver" class="org.apache.camel.jboss.JBossPackageScanClassResolver"/></programlisting>
+ <para>Another important configuration is the Camel Context declaration, as you can
see below:</para>
<programlisting><camelContext id="executionContext" xmlns="http://camel.apache.org/schema/spring" /></programlisting>
@@ -157,7 +158,8 @@
classes needs to be included in the JAXBContext. This will allow us to
copy our JAR model to the servlet container in which the drools-server
has been deployed and use them in JAXB commands without using a XSD
- file that declare the same model definition.<programlisting><drools-service:class>org.drools.model.Person</drools-service:class></programlisting></para>
+ file that declare the same model definition.</para>
+ <programlisting><drools-service:class>org.drools.model.Person</drools-service:class></programlisting>
<para>Also we can add commands that are going to be executed when
drools-server got deployed. To use this just add the next tag with the
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-introduction/src/main/docbook/en-US/Chapter-Install/Section-Maven_build.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-introduction/src/main/docbook/en-US/Chapter-Install/Section-Maven_build.xml 2010-07-26 12:36:03 UTC (rev 34185)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-introduction/src/main/docbook/en-US/Chapter-Install/Section-Maven_build.xml 2010-07-26 13:17:41 UTC (rev 34186)
@@ -96,7 +96,7 @@
calling <command>mvn package</command> in the drools-docs directory or adding the -Ddocumentation switch when you build the sources.
Documentation is generated into each drools-docs subdirectory's <filename>target/</filename> directory. Running <command>mvn -Ddocumentation package assembly:assembly</command>
in the Drools project root generates and copies the documentation into a zip file. This zip file is located in the root folders <filename>target/</filename>
- directory.
+ directory.</para>
<programlisting>[trikkola at trikkola trunk]$ mvn -Ddocumentation clean package assembly:assembly
[INFO] Scanning for projects...
@@ -195,7 +195,6 @@
[INFO] Finished at: Tue Apr 07 15:11:14 EEST 2009
[INFO] Final Memory: 48M/178M
[INFO] ------------------------------------------------------------------------></programlisting>
- </para>
<para>The generated manual can be found in the
<filename>target/drools-docs-$VERSION.jar</filename> file, a compressed archive with all formats.</para>
More information about the jboss-svn-commits
mailing list