[jboss-svn-commits] JBL Code SVN: r15268 - labs/jbossrules/trunk/documentation/manual/en/Chapter-Examples.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Sep 20 23:33:23 EDT 2007
Author: michael.neale at jboss.com
Date: 2007-09-20 23:33:23 -0400 (Thu, 20 Sep 2007)
New Revision: 15268
Modified:
labs/jbossrules/trunk/documentation/manual/en/Chapter-Examples/Section-Examples.xml
Log:
tweaks and corrections (BRMS and NumberGuess sections)
Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Examples/Section-Examples.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-Examples/Section-Examples.xml 2007-09-20 20:32:07 UTC (rev 15267)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Examples/Section-Examples.xml 2007-09-21 03:33:23 UTC (rev 15268)
@@ -1827,26 +1827,25 @@
</section>
<section>
- <section>
- <title>Number Guess</title>
+ <title>Number Guess</title>
- <programlisting><emphasis role="bold">Name:</emphasis> Number Guess
+ <programlisting><emphasis role="bold">Name:</emphasis> Number Guess
<emphasis role="bold">Main class:</emphasis> org.drools.examples.NumberGuessExample
<emphasis role="bold">Type:</emphasis> java application
<emphasis role="bold">Rules file:</emphasis> NumberGuess.drl
<emphasis role="bold">Objective:</emphasis> Demonstrate use of Rule Flow to organise Rules
</programlisting>
- <para>The "Number Guess" example shows the use of RuleFlow, a way of
- controlling the order in which rules are fired. It uses widely
- understood workflow diagrams to make clear the order that groups of
- rules will be executed.</para>
+ <para>The "Number Guess" example shows the use of RuleFlow, a way of
+ controlling the order in which rules are fired. It uses widely understood
+ workflow diagrams to make clear the order that groups of rules will be
+ executed.</para>
- <example>
- <title>Creating the Number Guess RuleBase - extract 1 from
- NumberGuessExample.java main() method</title>
+ <example>
+ <title>Creating the Number Guess RuleBase - extract 1 from
+ NumberGuessExample.java main() method</title>
- <programlisting>final PackageBuilder builder = new PackageBuilder();
+ <programlisting>final PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( new InputStreamReader(
ShoppingExample.class.getResourceAsStream( "NumberGuess.drl" ) ) );
@@ -1857,19 +1856,19 @@
ruleBase.addPackage( builder.getPackage() );
</programlisting>
- </example>
+ </example>
- <para>The creation of the package, and the loading of the rules (using
- the addPackageFromDrl() method ) is the same as the previous examples.
- There is a additional line to add the RuleFlow (NumberGuess.rfm) as you
- have the option of specifying different ruleflows for the same RuleBase.
- Otherwise the RuleBase is created in the same manner as before .</para>
+ <para>The creation of the package, and the loading of the rules (using the
+ addPackageFromDrl() method ) is the same as the previous examples. There
+ is a additional line to add the RuleFlow (NumberGuess.rfm) as you have the
+ option of specifying different ruleflows for the same RuleBase. Otherwise
+ the RuleBase is created in the same manner as before .</para>
- <example>
- <title>Starting the RuleFlow - extract 2 from NumberGuessExample.java
- main() method</title>
+ <example>
+ <title>Starting the RuleFlow - extract 2 from NumberGuessExample.java
+ main() method</title>
- <programlisting>final StatefulSession session = ruleBase.newStatefulSession();
+ <programlisting>final StatefulSession session = ruleBase.newStatefulSession();
session.insert( new GameRules( 100, 5 ) );
session.insert( new RandomNumber() );
@@ -1881,121 +1880,119 @@
session.dispose();
</programlisting>
- </example>
+ </example>
- <para>Once we have a RuleBase we can use it to obtain a stateful
- session. Into our session we insert our facts (standard Java Objects).
- For simplicity in this sample, these classes are all contained within
- our NumberGuessExample.java file. The GameRules class provides the
- maximum range and the number of guesses allowed. The RandomNumber class
- automatically generates a number between 0 and 100 and makes it
- available to our rules after insertion (via the getValue() method). The
- Game class keeps track of the guesses we have made before, and the
- number of guesses we have made.</para>
+ <para>Once we have a RuleBase we can use it to obtain a stateful session.
+ Into our session we insert our facts (standard Java Objects). For
+ simplicity in this sample, these classes are all contained within our
+ NumberGuessExample.java file. The GameRules class provides the maximum
+ range and the number of guesses allowed. The RandomNumber class
+ automatically generates a number between 0 and 100 and makes it available
+ to our rules after insertion (via the getValue() method). The Game class
+ keeps track of the guesses we have made before, and the number of guesses
+ we have made.</para>
- <para>Note that before we call the standard fireAllRules() method, we
- also start the process that we loaded earlier (via the startProcess()
- method). We explain where to obtain the parameter we pass ("Number
- Guess" - the id of the ruleflow) when we talk about the RuleFlow file
- and the graphical RuleFlow editor below.</para>
+ <para>Note that before we call the standard fireAllRules() method, we also
+ start the process that we loaded earlier (via the startProcess() method).
+ We explain where to obtain the parameter we pass ("Number Guess" - the id
+ of the ruleflow) when we talk about the RuleFlow file and the graphical
+ RuleFlow editor below.</para>
- <para>Before we finish we our Java code , we note that In 'real life' we
- would examine the final state of the objects (e.g. how many guesses it
- took, so that we could add it to a high score table). For this example
- we are content to ensure the working memory session is cleared by
- calling the dispose() method.</para>
+ <para>Before we finish we our Java code , we note that In 'real life' we
+ would examine the final state of the objects (e.g. how many guesses it
+ took, so that we could add it to a high score table). For this example we
+ are content to ensure the working memory session is cleared by calling the
+ dispose() method.</para>
- <figure>
- <title>RuleFlow for the NumberGuess Example</title>
+ <figure>
+ <title>RuleFlow for the NumberGuess Example</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="numberguess-ruleflow.png" />
- </imageobject>
- </mediaobject>
- </figure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="numberguess-ruleflow.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>If you open the NumberGuess.rf file open in the Drools IDE (and
- have the JBoss Rules extensions installed correctly in Eclipse) you
- should see the above diagram, similar to a standard flowchart. Its icons
- are similar (but not exactly the same) as the JBoss jBPM workflow
- product. Should you wish to edit the diagram, a menu of available
- components should be available to the left of the diagram in the IDE,
- which is call the pallete. This diagram is saved in a (almost human)
- readable xml format, using xstream.</para>
+ <para>If you open the NumberGuess.rf file open in the Drools IDE (and have
+ the JBoss Rules extensions installed correctly in Eclipse) you should see
+ the above diagram, similar to a standard flowchart. Its icons are similar
+ (but not exactly the same) as the JBoss jBPM workflow product. Should you
+ wish to edit the diagram, a menu of available components should be
+ available to the left of the diagram in the IDE, which is call the
+ pallete. This diagram is saved in a (almost human) readable xml format,
+ using xstream.</para>
- <para>If it is not already open, ensure the properties view is visible
- in the IDE. It can opened by selecting Window -> Show View ->
- Other and then select the Properties view. If you do this <emphasis
- role="bold">before</emphasis> you select any item on the RuleFlow (or
- click on blank space in the RuleFlow) you should be presented with the
- following set of properties.</para>
+ <para>If it is not already open, ensure the properties view is visible in
+ the IDE. It can opened by selecting Window -> Show View -> Other and
+ then select the Properties view. If you do this <emphasis
+ role="bold">before</emphasis> you select any item on the RuleFlow (or
+ click on blank space in the RuleFlow) you should be presented with the
+ following set of properties.</para>
- <figure>
- <title>Properties for the Number Guess RuleFlow</title>
+ <figure>
+ <title>Properties for the Number Guess RuleFlow</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="numberguess-ruleflow-properties.png" />
- </imageobject>
- </mediaobject>
- </figure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="numberguess-ruleflow-properties.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>Keep an eye on the properties view as we progress through the
- example RuleFlow as it gives valuable information. In this case it
- provides us with the ID of the RuleFlow process that we used in our
- earlier code example when we called session.startprocess().</para>
+ <para>Keep an eye on the properties view as we progress through the
+ example RuleFlow as it gives valuable information. In this case it
+ provides us with the ID of the RuleFlow process that we used in our
+ earlier code example when we called session.startprocess().</para>
- <para>To give an overview of each of the node types (boxes) in the
- NumberGuess RuleFlow.</para>
+ <para>To give an overview of each of the node types (boxes) in the
+ NumberGuess RuleFlow.</para>
- <para>
- <itemizedlist>
- <listitem>
- <para>The Start and End nodes (green arrow and red box) are where
- the RuleFlow starts and ends.</para>
- </listitem>
+ <para><itemizedlist>
+ <listitem>
+ <para>The Start and End nodes (green arrow and red box) are where
+ the RuleFlow starts and ends.</para>
+ </listitem>
- <listitem>
- <para>RuleFlowGroup (simple yellow box). These map to the
- RuleFlowGroups in our rules (DRL) file that we will look at later.
- For example when the flow reaches the 'Too High' RuleFlowGroup,
- only those rules marked with an attribute of <emphasis
- role="bold">ruleflow-group "Too High" </emphasis> can potentially
- fire.</para>
- </listitem>
+ <listitem>
+ <para>RuleFlowGroup (simple yellow box). These map to the
+ RuleFlowGroups in our rules (DRL) file that we will look at later.
+ For example when the flow reaches the 'Too High' RuleFlowGroup, only
+ those rules marked with an attribute of <emphasis
+ role="bold">ruleflow-group "Too High" </emphasis> can potentially
+ fire.</para>
+ </listitem>
- <listitem>
- <para>Action Nodes (yellow box with cog like icon). These can
- perform standard Java method calls. Most action nodes in this
- example call System.out.println to give an indication to the user
- of what is going on.</para>
- </listitem>
+ <listitem>
+ <para>Action Nodes (yellow box with cog like icon). These can
+ perform standard Java method calls. Most action nodes in this
+ example call System.out.println to give an indication to the user of
+ what is going on.</para>
+ </listitem>
- <listitem>
- <para>Split and Join Nodes (Blue Ovals) such as "Guess Correct"
- and "More Guesses Join" where the flow of control can split
- (according to various conditions) and / or rejoin.</para>
- </listitem>
+ <listitem>
+ <para>Split and Join Nodes (Blue Ovals) such as "Guess Correct" and
+ "More Guesses Join" where the flow of control can split (according
+ to various conditions) and / or rejoin.</para>
+ </listitem>
- <listitem>
- <para>Arrows that indicate the flow between the various
- nodes.</para>
- </listitem>
- </itemizedlist>
- </para>
+ <listitem>
+ <para>Arrows that indicate the flow between the various
+ nodes.</para>
+ </listitem>
+ </itemizedlist></para>
- <para>These various nodes work together with the Rules to make the
- Number Guess game work. For example, the "Guess" RuleFlowGroup allows
- only the rule "Get user Guess" to fire (details below) as only that Rule
- has a matching attribute of <emphasis role="bold">ruleflow-group
- "Guess"</emphasis></para>
+ <para>These various nodes work together with the Rules to make the Number
+ Guess game work. For example, the "Guess" RuleFlowGroup allows only the
+ rule "Get user Guess" to fire (details below) as only that Rule has a
+ matching attribute of <emphasis role="bold">ruleflow-group
+ "Guess"</emphasis></para>
- <example>
- <title>A Rule that will fire only a specific point in the RuleFlow -
- extract from NumberGuess.drl</title>
+ <example>
+ <title>A Rule that will fire only a specific point in the RuleFlow -
+ extract from NumberGuess.drl</title>
- <programlisting>rule "Get user Guess"
+ <programlisting>rule "Get user Guess"
ruleflow-group "Guess"
no-loop
when
@@ -2014,97 +2011,95 @@
end
</programlisting>
- </example>
+ </example>
- <para>The rest of this rule is fairly standard : The <emphasis
- role="bold">LHS (when)</emphasis> section of the rule states that it
- will be activated for each <emphasis>RandomNumber</emphasis> object
- inserted into the working memory where <emphasis>guessCount</emphasis>
- is less than the <emphasis>allowedGuesses</emphasis> ( read from the
- GameRules Class) and where the user has not guessed the correct
- number.</para>
+ <para>The rest of this rule is fairly standard : The <emphasis
+ role="bold">LHS (when)</emphasis> section of the rule states that it will
+ be activated for each <emphasis>RandomNumber</emphasis> object inserted
+ into the working memory where <emphasis>guessCount</emphasis> is less than
+ the <emphasis>allowedGuesses</emphasis> ( read from the GameRules Class)
+ and where the user has not guessed the correct number.</para>
- <para>The <emphasis role="bold">RHS (consequence, then)</emphasis>
- prints a message to the user, then awaits user input from
- <emphasis>System.in. </emphasis> After getting this input (as System.in
- blocks until the <return> key is pressed) it updates/modifes the
- guess count, the actual guess and makes both available in the working
- memory.</para>
+ <para>The <emphasis role="bold">RHS (consequence, then)</emphasis> prints
+ a message to the user, then awaits user input from <emphasis>System.in.
+ </emphasis> After getting this input (as System.in blocks until the
+ <return> key is pressed) it updates/modifes the guess count, the
+ actual guess and makes both available in the working memory.</para>
- <para>The rest of the Rules file is fairly standard ; the package
- declares the dialect is set to MVEL, various Java classes are imported.
- In total, there are five rules in this file:</para>
+ <para>The rest of the Rules file is fairly standard ; the package declares
+ the dialect is set to MVEL, various Java classes are imported. In total,
+ there are five rules in this file:</para>
- <para><orderedlist>
- <listitem>
- <para>Get User Guess, the Rule we examined above.</para>
- </listitem>
+ <para><orderedlist>
+ <listitem>
+ <para>Get User Guess, the Rule we examined above.</para>
+ </listitem>
- <listitem>
- <para>A Rule to record the highest guess.</para>
- </listitem>
+ <listitem>
+ <para>A Rule to record the highest guess.</para>
+ </listitem>
- <listitem>
- <para>A Rule to record the lowest guess.</para>
- </listitem>
+ <listitem>
+ <para>A Rule to record the lowest guess.</para>
+ </listitem>
- <listitem>
- <para>A Rule to inspect the guess and retract it from memory if
- incorrect.</para>
- </listitem>
+ <listitem>
+ <para>A Rule to inspect the guess and retract it from memory if
+ incorrect.</para>
+ </listitem>
- <listitem>
- <para>A Rule that notifies the user that all guesses have been
- used up.</para>
- </listitem>
- </orderedlist>One point of integration between the standard Rules and
- the RuleFlow is via the 'ruleflow-group' attribute on the rules (as
- dicussed above). A <emphasis role="bold">second point of integration
- between the Rules File (drl) and the Rules Flow .rf files </emphasis>is
- that the Split Nodes (the blue ovals) can use values in working memory
- (as updated by the Rules) to decide which flow of action to take. To see
- how this works click on the "Guess Correct Node" ; then within the
- properties view, open the constraints editor (the button at the right
- that appears once you click on the 'Constraints' property line). You
- should see something similar to the Diagram below.</para>
+ <listitem>
+ <para>A Rule that notifies the user that all guesses have been used
+ up.</para>
+ </listitem>
+ </orderedlist>One point of integration between the standard Rules and
+ the RuleFlow is via the 'ruleflow-group' attribute on the rules (as
+ dicussed above). A <emphasis role="bold">second point of integration
+ between the Rules File (drl) and the Rules Flow .rf files </emphasis>is
+ that the Split Nodes (the blue ovals) can use values in working memory (as
+ updated by the Rules) to decide which flow of action to take. To see how
+ this works click on the "Guess Correct Node" ; then within the properties
+ view, open the constraints editor (the button at the right that appears
+ once you click on the 'Constraints' property line). You should see
+ something similar to the Diagram below.</para>
- <figure>
- <title>Edit Constraints for the GuessCorrect Node</title>
+ <figure>
+ <title>Edit Constraints for the GuessCorrect Node</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="numberguess-editconstraints.png" />
- </imageobject>
- </mediaobject>
- </figure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="numberguess-editconstraints.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>Click on 'Edit' beside 'To node Too High' and you see a dialog
- like the one below. The values in the 'Textual Editor' follow the
- standard Rule Format (LHS) and can refer to objects in working memory.
- The consequence (RHS) is that the flow of control follows this node
- (i.e. To node Too high') if the LHS expression evaluates to true.</para>
+ <para>Click on 'Edit' beside 'To node Too High' and you see a dialog like
+ the one below. The values in the 'Textual Editor' follow the standard Rule
+ Format (LHS) and can refer to objects in working memory. The consequence
+ (RHS) is that the flow of control follows this node (i.e. To node Too
+ high') if the LHS expression evaluates to true.</para>
- <figure>
- <title>Constraints Editor for the GuessCorrect Node / value too
- high</title>
+ <figure>
+ <title>Constraints Editor for the GuessCorrect Node / value too
+ high</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="numberguess-constraint-toohigh.png" />
- </imageobject>
- </mediaobject>
- </figure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="numberguess-constraint-toohigh.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>Since the NumberGuess.java example contains a main() method, it
- can be run as a standard Java application (either from the command line
- or via the IDE). A typical game might result in the interaction below
- (the numbers in bold are typed in by the user).</para>
+ <para>Since the NumberGuess.java example contains a main() method, it can
+ be run as a standard Java application (either from the command line or via
+ the IDE). A typical game might result in the interaction below (the
+ numbers in bold are typed in by the user).</para>
- <example>
- <title>Example Console output where the Number Guess Example beat the
- human!</title>
+ <example>
+ <title>Example Console output where the Number Guess Example beat the
+ human!</title>
- <programlisting>You have 5 out of 5 guesses left.
+ <programlisting>You have 5 out of 5 guesses left.
Please enter your guess from 0 to 100
<emphasis role="bold">50</emphasis>
Your guess was too high
@@ -2128,77 +2123,74 @@
The correct guess was 48
</programlisting>
- </example>
+ </example>
- <para>A summary of what is happening in this sample is:</para>
+ <para>A summary of what is happening in this sample is:</para>
- <para>
- <orderedlist>
- <listitem>
- <para>Main() method of NumberGuessExample.java loads RuleBase,
- gets a StatefulSession and inserts Game, GameRules and
- RandomNumber (containing the target number) objects into it. This
- method sets the process flow we are going to use, and fires all
- rules. Control passes to the RuleFlow.</para>
- </listitem>
+ <para><orderedlist>
+ <listitem>
+ <para>Main() method of NumberGuessExample.java loads RuleBase, gets
+ a StatefulSession and inserts Game, GameRules and RandomNumber
+ (containing the target number) objects into it. This method sets the
+ process flow we are going to use, and fires all rules. Control
+ passes to the RuleFlow.</para>
+ </listitem>
- <listitem>
- <para>The NumberGuess.rf RuleFlow begins at the Start node.</para>
- </listitem>
+ <listitem>
+ <para>The NumberGuess.rf RuleFlow begins at the Start node.</para>
+ </listitem>
- <listitem>
- <para>Control passes (via the "more guesses" join node) to the
- Guess Node..</para>
- </listitem>
+ <listitem>
+ <para>Control passes (via the "more guesses" join node) to the Guess
+ Node..</para>
+ </listitem>
- <listitem>
- <para>At the Guess node, the appropriate RuleFlowGroup ("Get user
- Guess") is enabled. In this case the Rule "Guess" (in the
- NumberGuess.drl file) is triggered. This rule displays a message
- to the user, takes the response, and puts it into memory. Flow
- passes to the next Rule Flow Node.</para>
- </listitem>
+ <listitem>
+ <para>At the Guess node, the appropriate RuleFlowGroup ("Get user
+ Guess") is enabled. In this case the Rule "Guess" (in the
+ NumberGuess.drl file) is triggered. This rule displays a message to
+ the user, takes the response, and puts it into memory. Flow passes
+ to the next Rule Flow Node.</para>
+ </listitem>
- <listitem>
- <para>At the next node , "Guess Correct", constraints inspect the
- current session and decide which path we take next.</para>
+ <listitem>
+ <para>At the next node , "Guess Correct", constraints inspect the
+ current session and decide which path we take next.</para>
- <para>If the guess in step 4 was too high / too low flow procees
- along a path which has (i) An action node with normal Java code
- prints a too high / too low statement and (ii) a RuleFlowGroup
- causes a highest guess / lowest guess Rule to be triggered in the
- Rules file. Flow passes from these nodes to step 6.</para>
+ <para>If the guess in step 4 was too high / too low flow procees
+ along a path which has (i) An action node with normal Java code
+ prints a too high / too low statement and (ii) a RuleFlowGroup
+ causes a highest guess / lowest guess Rule to be triggered in the
+ Rules file. Flow passes from these nodes to step 6.</para>
- <para>If the guess in step 4 just right we proceed along the path
- towards the end of the Rule Flow. Before we get there, an action
- node with normal Java code prints a statement "you guessed
- correctly". There is a join node here (just before the Rule Flow
- End) so that our no-more-guesses path (step 7) can also terminate
- the RuleFlow.</para>
- </listitem>
+ <para>If the guess in step 4 just right we proceed along the path
+ towards the end of the Rule Flow. Before we get there, an action
+ node with normal Java code prints a statement "you guessed
+ correctly". There is a join node here (just before the Rule Flow
+ End) so that our no-more-guesses path (step 7) can also terminate
+ the RuleFlow.</para>
+ </listitem>
- <listitem>
- <para>Control passes as per the RuleFlow via a join node, a guess
- incorrect RuleFlowGroup (triggers a rule to retract a guess from
- working memory) onto the "more guesses" decision node.</para>
- </listitem>
+ <listitem>
+ <para>Control passes as per the RuleFlow via a join node, a guess
+ incorrect RuleFlowGroup (triggers a rule to retract a guess from
+ working memory) onto the "more guesses" decision node.</para>
+ </listitem>
- <listitem>
- <para>The "more guesses" decision node (right hand side of
- ruleflow) uses constraints (again looking at values that the Rules
- have put into the working memory) to decide if we have more
- guesses and if so, goto step 3. If not we proceed to the end of
- the workflow, via a RuleFlowGroup that triggers a rule stating
- "you have no more guesses".</para>
- </listitem>
+ <listitem>
+ <para>The "more guesses" decision node (right hand side of ruleflow)
+ uses constraints (again looking at values that the Rules have put
+ into the working memory) to decide if we have more guesses and if
+ so, goto step 3. If not we proceed to the end of the workflow, via a
+ RuleFlowGroup that triggers a rule stating "you have no more
+ guesses".</para>
+ </listitem>
- <listitem>
- <para>The Loop 3-7 continues until the number is guessed
- correctly, or we run out of guesses.</para>
- </listitem>
- </orderedlist>
- </para>
- </section>
+ <listitem>
+ <para>The Loop 3-7 continues until the number is guessed correctly,
+ or we run out of guesses.</para>
+ </listitem>
+ </orderedlist></para>
</section>
<section>
@@ -2819,8 +2811,10 @@
</literallayout>
</section>
</section>
+
<section>
- <title>The real world example - Insurance Company Risk Factor and Policy price</title>
+ <title>Insurance Company Risk Factor and Policy price (using BRMS)</title>
+
<programlisting><emphasis role="bold">Name:</emphasis> drools-insurance
<emphasis role="bold">Type:</emphasis> java web application
<emphasis role="bold">Rules file:</emphasis> exported repository from brms, repository_export.xml
@@ -2840,135 +2834,152 @@
study and practice.</para>
</section>
- <section>
- <title>The insurance logic</title>
+ <section>
+ <title>The insurance logic</title>
- <para>
- If you have a poor driving record, you may need to look into high risk auto insurance. Accidents increase these rates as well.
- If you have a low experience for example less than 3 years as a licensed driver, insurance companies believe that the chances
- that you will be involved in a traffic accident are higher than someone more expert.
- </para>
+ <para>If you have a poor driving record, you may need to look into high
+ risk auto insurance. Accidents increase these rates as well. If you have
+ a low experience for example less than 3 years as a licensed driver,
+ insurance companies believe that the chances that you will be involved
+ in a traffic accident are higher than someone more expert.</para>
- <para>
- Who you are also plays a factor. Men are considered more of a risk than women. Teens are considered more of a risk than adults as
- well if you have some younger driver in family like your 20 years old son.
-<programlisting>
-rule "Young male single driver"
+ <para>Who you are also plays a factor. Men are considered more of a risk
+ than women. Teens are considered more of a risk than adults as well if
+ you have some younger driver in family like your 20 years old son.
+ <programlisting>
+rule "Young male single driver"
ruleflow-group "risk assessment"
when
- $driver : Driver( genre == Driver.MALE, age < 25, maritalState == Driver.SINGLE )
+ $driver : Driver( genre == Driver.MALE, age < 25, maritalState == Driver.SINGLE )
then
- $driver.updateInsuranceFactor(1.6);
+ $driver.updateInsuranceFactor(1.6);
end
rule "no expert driver"
ruleflow-group "risk assessment"
when
- $driver : Driver ( licenceYears < 3 )
+ $driver : Driver ( licenceYears < 3 )
then
- $driver.updateInsuranceFactor(1.2);
+ $driver.updateInsuranceFactor(1.2);
end
-</programlisting>
+</programlisting></para>
- </para>
-
- <para>
- Extra coverage over glasses, additional car and accessories, like your expansive "pimped" sound system will increase your
- insurance final price, not the risk factor.
- <programlisting>
+ <para>Extra coverage over glasses, additional car and accessories, like
+ your expansive "pimped" sound system will increase your insurance final
+ price, not the risk factor. <programlisting>
ruleflow-group "insurancecalcule"
salience 20
when
- not Rejection()
- $driver : Driver ( driverID : id )
- $access : AccessoriesCoverage ( driverId == driverID)
- $policy : Policy( approved == true )
+ not Rejection()
+ $driver : Driver ( driverID : id )
+ $access : AccessoriesCoverage ( driverId == driverID)
+ $policy : Policy( approved == true )
then
- $policy.setInsurancePrice( $policy.getInsurancePrice() +
- ($access.getAlarmSystemValue() * 0.10) +
- ($access.getArmorValue() * 0.20) +
- ($access.getSoundSystemValue() * 0.30 ));
-</programlisting>
- </para>
+ $policy.setInsurancePrice( $policy.getInsurancePrice() +
+ ($access.getAlarmSystemValue() * 0.10) +
+ ($access.getArmorValue() * 0.20) +
+ ($access.getSoundSystemValue() * 0.30 ));
+</programlisting></para>
- <para>This example uses the previously explained <emphasis role="bold">RuleFlow</emphasis> feature, the following diagram gives you an overview
- of the insurance factor and calculate logic: As you can see, we first calculate the insurance factor, if the driver matches with some
- rejection condition we don't execute the group that contains the Policy price calculus, just returning and not approved policy
- <para><programlisting>
+ <para>This example uses the previously explained <emphasis
+ role="bold">RuleFlow</emphasis> feature, the following diagram gives you
+ an overview of the insurance factor and calculate logic: As you can see,
+ we first calculate the insurance factor, if the driver matches with some
+ rejection condition we don't execute the group that contains the Policy
+ price calculus, just returning and not approved policy <para>
+ <programlisting>
ruleflow-group "insurancecalcule"
salience 10
when
- not Rejection()
- $driver : Driver(ifactor : insuranceFactor)
- $policy : Policy( approved == true, bp : basePrice, ip : insurancePrice )
+ not Rejection()
+ $driver : Driver(ifactor : insuranceFactor)
+ $policy : Policy( approved == true, bp : basePrice, ip : insurancePrice )
then
- $policy.setInsurancePrice((bp * ifactor) + ip);
-</programlisting></para>
+ $policy.setInsurancePrice((bp * ifactor) + ip);
+</programlisting>
+ </para></para>
- </para>
- <para>
- <figure>
- <title>The insurance rule flow</title>
+ <para><figure>
+ <title>The insurance rule flow</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="insurance-ruleflow.png"
- format="PNG" scalefit="1" />
- </imageobject>
- </mediaobject>
- </figure>
- </para>
- </section>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="insurance-ruleflow.png"
+ format="PNG" scalefit="1" />
+ </imageobject>
+ </mediaobject>
+ </figure></para>
+ </section>
- <section>
- <title>Downloading and installing the BRMS</title>
- <itemizedlist>
- <listitem>
- <para>Download the latest version of BRMS from http://cruisecontrol.jboss.com/cc/artifacts/jboss-rules</para>
- </listitem>
- <listitem>
- <para>Deploy BRMS WAR file into JBoss4.2 AS or JBossWeb, other containers can be used as well
- possibly with some tweaking of dependencies (check this url if you using a different application server http://wiki.jboss.org/wiki/Wiki.jsp?page=JBRMSjsfdependencies).</para>
- </listitem>
- <listitem>
- <para>Check you can access and run the BRMS.</para>
- </listitem>
- <listitem>
- <para>Check out the demo project from the Drools subversion repository
- http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-examples/drools-insurance/</para>
- </listitem>
- <listitem>
- <para>Import the demo business rules insurance repository file into BRMS, the compressed can be found at "files" folder in the
- demo project. To do this, open the "files" directory, unzip the file there locally, and then go to the "Admin" section and
- "Manage import/export" of the BRMS, select the file, and press "Import" - follow instructions.</para>
- </listitem>
+ <section>
+ <title>Downloading and installing the BRMS</title>
- <listitem>
- <para>Navigate through the BRMS web application to see how things are placed and organized and try to create some rules.</para>
- </listitem>
+ <itemizedlist>
+ <listitem>
+ <para>Download the latest version of BRMS from
+ http://cruisecontrol.jboss.com/cc/artifacts/jboss-rules</para>
+ </listitem>
- <listitem>
- <para>Go to the "Packages" feature and build the package (you should see no errors).</para>
- </listitem>
+ <listitem>
+ <para>Deploy BRMS WAR file into JBoss4.2 AS or JBossWeb, other
+ containers can be used as well possibly with some tweaking of
+ dependencies (check this url if you using a different application
+ server
+ http://wiki.jboss.org/wiki/Wiki.jsp?page=JBRMSjsfdependencies).</para>
+ </listitem>
- <listitem>
- <para>Now go to the "Deployment" feature, when you click on the package, it will show you one snapshot (which was part of the
- import, you can create more if you like from the previous step).</para>
- </listitem>
- </itemizedlist>
- </section>
+ <listitem>
+ <para>Check you can access and run the BRMS.</para>
+ </listitem>
- <section>
- <title>Deploying the insurance example in your application server</title>
- <itemizedlist>
- <listitem>
- <para>Go into your downloaded project and execute <programlisting>mvn clean package</programlisting></para>
- </listitem>
+ <listitem>
+ <para>Check out the demo project from the Drools subversion
+ repository
+ http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-examples/drools-insurance/</para>
+ </listitem>
- <listitem>
- <para> You should see the RuleAgent downloadomg the pre-compiled package from brms, if something goes wrong and all tests fails,
- check if the BRMS is up and running and try rebuild the package snapshot.
- <programlisting>Running org.acme.insurance.test.DriverTest
+ <listitem>
+ <para>Import the demo business rules insurance repository file into
+ BRMS, the compressed can be found at "files" folder in the demo
+ project. To do this, open the "files" directory, unzip the file
+ there locally, and then go to the "Admin" section and "Manage
+ import/export" of the BRMS, select the file, and press "Import" -
+ follow instructions.</para>
+ </listitem>
+
+ <listitem>
+ <para>Navigate through the BRMS web application to see how things
+ are placed and organized and try to create some rules.</para>
+ </listitem>
+
+ <listitem>
+ <para>Go to the "Packages" feature and build the package (you should
+ see no errors).</para>
+ </listitem>
+
+ <listitem>
+ <para>Now go to the "Deployment" feature, when you click on the
+ package, it will show you one snapshot (which was part of the
+ import, you can create more if you like from the previous
+ step).</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Deploying the insurance example in your application
+ server</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>Go into your downloaded project and execute <programlisting>mvn clean package</programlisting></para>
+ </listitem>
+
+ <listitem>
+ <para>You should see the RuleAgent downloadomg the pre-compiled
+ package from brms, if something goes wrong and all tests fails,
+ check if the BRMS is up and running and try rebuild the package
+ snapshot. <programlisting>Running org.acme.insurance.test.DriverTest
RuleAgent(insuranceconfig) INFO (Wed Sep 18 14:11:44 BRT 2007): Configuring with newInstance=true, secondsToRefresh=30
RuleAgent(insuranceconfig) INFO (Wed Sep 18 14:11:44 BRT 2007): Configuring package provider : URLScanner monitoring URLs:
http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/org.acme.insurance.base/InsuranceDemo
@@ -3002,32 +3013,32 @@
Results :
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
- </programlisting></para>
- </listitem>
- </itemizedlist>
- </section>
+</programlisting></para>
+ </listitem>
+ </itemizedlist>
+ </section>
- <section>
- <title>Running the example from the web page</title>
- <para>After running and packing you are able to deploy the war into your application server, just following the previous instructions
- for BRMS, then point your browser to the example url, that should be something like this http://localhost:8080/drools-insurance.
- Just play around the example and change some values and press the execute button, after the rules fired the result will be displayed in the bottom of the page.
- </para>
-
- <para>
- <figure>
- <title>The insurance web page</title>
+ <section>
+ <title>Running the example from the web page</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="insurance-website.png"
- format="PNG" scalefit="2" />
- </imageobject>
- </mediaobject>
- </figure>
- </para>
- </section>
+ <para>After running and packing you are able to deploy the war into your
+ application server, just following the previous instructions for BRMS,
+ then point your browser to the example url, that should be something
+ like this http://localhost:8080/drools-insurance. Just play around the
+ example and change some values and press the execute button, after the
+ rules fired the result will be displayed in the bottom of the
+ page.</para>
+ <para><figure>
+ <title>The insurance web page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="insurance-website.png"
+ format="PNG" scalefit="2" />
+ </imageobject>
+ </mediaobject>
+ </figure></para>
+ </section>
</section>
</section>
\ No newline at end of file
More information about the jboss-svn-commits
mailing list