[jboss-svn-commits] JBL Code SVN: r20476 - in labs/jbossrules/trunk/drools-docs: drools-docs-examples and 7 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri Jun 13 18:34:41 EDT 2008
Author: mark.proctor at jboss.com
Date: 2008-06-13 18:34:41 -0400 (Fri, 13 Jun 2008)
New Revision: 20476
Removed:
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Thumbs.db
Modified:
labs/jbossrules/trunk/drools-docs/drools-docs-examples/pom.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Section-Examples.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/master.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/pom.xml
labs/jbossrules/trunk/drools-docs/drools-docs-flow/pom.xml
labs/jbossrules/trunk/drools-docs/drools-docs-fusion/pom.xml
labs/jbossrules/trunk/drools-docs/drools-docs-guvnor/pom.xml
labs/jbossrules/trunk/drools-docs/drools-docs-solver/pom.xml
labs/jbossrules/trunk/drools-docs/pom.xml
Log:
JBRULES-1643
-Starts to moved Drools expert examples into own folders
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-examples/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-examples/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-examples/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -14,93 +14,4 @@
<packaging>jdocbook</packaging>
<name>Drools :: Documentation :: Drools Examples</name>
<description>Examples and Tutorials</description>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Section-Examples.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Section-Examples.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Section-Examples.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -1,1276 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-<section>
+<section xmlns:xi="http://www.w3.org/2001/XInclude">
<title></title>
<section>
<title>Getting the examples</title>
<para>Make sure the Drools Eclipse plugin is installed, which needs GEF dependency installed first. Then download and extract the drools-examples zip file, which includes an already created Eclipse project. Import that project into a new Eclipse workspace. The rules all have example classes that execute the rules. If you want to try the examples in another project (or another IDE) then you will need to setup the dependencies by hand of course. Many, but not all of the examples are documented below, enjoy :)</para>
- </section>
- <section>
- <title>Hello World</title>
+ </section>
- <screen><emphasis role="bold">Name:</emphasis> Hello World
-<emphasis role="bold">Main class:</emphasis> org.drools.examples.HelloWorldExample
-<emphasis role="bold">Type:</emphasis> java application
-<emphasis role="bold">Rules file:</emphasis> HelloWorld.drl
-<emphasis role="bold">Objective:</emphasis> demonstrate basic rules in use</screen>
+ <xi:include href="Section-HelloWorldExample.xml" />
+ <xi:include href="Section-StateExample.xml" />
+ <xi:include href="Section-FibonacciExample.xml" />
+ <xi:include href="Section-BankingExample.xml" />
-
- <para>The "Hello World" example shows a simple example of rules usage, and both the MVEL and Java dialects.</para>
-
- <para>In this example it will be shown how to build rulebases and sessions and how to add audit logging and debug outputs, this information is ommitted from other examples as it's all very similar. PackageBuilder is used to turn a drl source file into Package objects which the RuleBase can consume, addPackageFromDrl takes a Reader interface as the parameter. Reader can be used to retrieve a source drl file from various locations, in this case the drl file is being retrieved from the classpath as an InputStream which we turn into a Reader by wrapping it with InputStreamReader; but it could come the disk or a url. The use of the Reader interface means that Drools does not have to care. In this case we only add a single drl source file, but multiple drl files can be added and all are merged into a single Package. All drl files added to the PackageBuilder must declare themselves in the same package namespace, if you wish to build a Package in a different namespace a new insta!
nce of PackageBuilder must be created; multiple packages of differerent namespaces can be added to the same RuleBase. When all the drl files have been added we should check the builder for errors; while the RuleBase will validate the packge it will only have access to the error information as a String, so if you wish to debug the error information you should do it on the builder instance. Once we know the builder is error free get the Package, instantiate a RuleBase from the RuleBaseFactory and add the package.</para>
-
- <example>
- <title>HelloWorld example: Creating the RuleBase and Session</title>
-
- <programlisting>//read in the source
-Reader source = new InputStreamReader( HelloWorldExample.class.getResourceAsStream( "HelloWorld.drl" ) );
-
-PackageBuilder builder = new PackageBuilder();
-
-//this will parse and compile in one step
-builder.addPackageFromDrl( source );
-
-// Check the builder for errors
-if ( builder.hasErrors() ) {
- System.out.println( builder.getErrors().toString() );
- throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
-}
-
-//get the compiled package (which is serializable)
-Package pkg = builder.getPackage();
-
-//add the package to a rulebase (deploy the rule package).
-RuleBase ruleBase = RuleBaseFactory.newRuleBase();
-ruleBase.addPackage( pkg );
-
-StatefulSession session = ruleBase.newStatefulSession();</programlisting>
- </example>
-
- <para>Drools has an event model that exposes much of what's happening internally, two default debug listeners are supplied DebugAgendaEventListener and DebugWorkingMemoryEventListener which print out debug event information to the err console, adding listeners to a session is trivial and shown below. The WorkingMemoryFileLogger provides execution auditing which can be viewed in a graphical viewer; it's actually a specialised implementation built on the agenda and working memory listeners, when the engine has finished executing logger.writeToDisk() must be called.</para>
-
- <para>Most of the examples use the Audit logging features of Drools to record execution flow for later inspection.</para>
-
- <example>
- <title>HelloWorld example: Event logging and Auditing</title>
-
- <programlisting>// setup the debug listeners
-session.addEventListener( new DebugAgendaEventListener() );
-session.addEventListener( new DebugWorkingMemoryEventListener() );
-
-// setup the audit logging
-WorkingMemoryFileLogger logger = new WorkingMemoryFileLogger( session );
-logger.setFileName( "log/helloworld" ); </programlisting>
- </example>
-
- <para>The single class used in this example is very simple, it has two fields: the message, which is a String and the status which can be either the int HELLO or the int GOODBYE.</para>
-
- <example>
- <title>HelloWorld example: Message Class</title>
-
- <programlisting>public static class Message {
- public static final int HELLO = 0;
- public static final int GOODBYE = 1;
-
- private String message;
- private int status;
- ...
-}</programlisting>
- </example>
-
- <para>A single Message object is created with the message "Hello World" and status HELLO and then inserted into the engine, at which point fireAllRules() is executed. Remember all the network evaluation is done during the insert time, by the time the program execution reaches the fireAllRules() method it already knows which rules are fully matches and able to fire.</para>
-
- <example>
- <title>HelloWorld example: Execution</title>
-
- <programlisting>Message message = new Message();
-message.setMessage( "Hello World" );
-message.setStatus( Message.HELLO );
-session.insert( message );
-
-session.fireAllRules();
-
-logger.writeToDisk();
-
-session.dispose(); </programlisting>
- </example>
-
- <para>To execute the example from Java.</para>
-
- <orderedlist>
- <listitem>
- <para>Open the class org.drools.examples.FibonacciExample in your Eclipse IDE</para>
- </listitem>
-
- <listitem>
- <para>Right-click the class an select "Run as..." -> "Java application"</para>
- </listitem>
- </orderedlist>
-
- <para>If we put a breakpoint on the fireAllRules() method and select the session variable we can see that the "Hello World" view is already activated and on the Agenda, showing that all the pattern matching work was already done during the insert.</para>
-
- <figure>
- <title>Hello World : fireAllRules Agenda View</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="helloworld_agenda1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The may application print outs go to to System.out while the debug listener print outs go to System.err.</para>
-
- <example>
- <title>HelloWorld example: Console.out</title>
-
- <programlisting>Hello World
-Goodbye cruel world</programlisting>
- </example>
-
- <example>
- <title>HelloWorld example: Console.err</title>
-
- <programlisting>==>[ActivationCreated(0): rule=Hello World;
- tuple=[fid:1:1:org.drools.examples.HelloWorldExample$Message at 17cec96]]
-[ObjectInserted: handle=[fid:1:1:org.drools.examples.HelloWorldExample$Message at 17cec96];
- object=org.drools.examples.HelloWorldExample$Message at 17cec96]
-[BeforeActivationFired: rule=Hello World;
- tuple=[fid:1:1:org.drools.examples.HelloWorldExample$Message at 17cec96]]
-==>[ActivationCreated(4): rule=Good Bye;
- tuple=[fid:1:2:org.drools.examples.HelloWorldExample$Message at 17cec96]]
-[ObjectUpdated: handle=[fid:1:2:org.drools.examples.HelloWorldExample$Message at 17cec96];
- old_object=org.drools.examples.HelloWorldExample$Message at 17cec96;
- new_object=org.drools.examples.HelloWorldExample$Message at 17cec96]
-[AfterActivationFired(0): rule=Hello World]
-[BeforeActivationFired: rule=Good Bye;
- tuple=[fid:1:2:org.drools.examples.HelloWorldExample$Message at 17cec96]]
-[AfterActivationFired(4): rule=Good Bye] </programlisting>
- </example>
-
- <para>The <emphasis role="bold">LHS (when)</emphasis> section of the rule states that it will be activated for each <emphasis>Message</emphasis> object inserted into the working memory whose <emphasis>status</emphasis> is <emphasis>Message.HELLO</emphasis>. Besides that, two variable binds are created: "<emphasis>message</emphasis>" variable is bound to the <emphasis>message</emphasis> attribute and "<emphasis>m</emphasis>" variable is bound to the <emphasis>object matched pattern</emphasis> itself.</para>
-
- <para>The <emphasis role="bold">RHS (consequence, then)</emphasis> section of the rule is written using the MVEL expression language, as declared by the rule's attribute <emphasis>dialect</emphasis>. After printing the content of the <emphasis>message</emphasis> bound variable to the default console, the rule changes the values of the <emphasis>message</emphasis> and <emphasis>status</emphasis> attributes of the <emphasis>m</emphasis> bound variable; using MVEL's 'modify' keyword which allows you to apply a block of setters in one statement, with the engine being automatically notified of the changes at the end of the block.</para>
-
- <example>
- <title>HelloWorld example: rule "Hello World"</title>
-
- <programlisting>rule "Hello World"
- dialect "mvel"
- when
- m : Message( status == Message.HELLO, message : message )
- then
- System.out.println( message );
- modify ( m ) { message = "Goodbyte cruel world",
- status = Message.GOODBYE };
-end</programlisting>
- </example>
-
- <para>We can add a break point into the DRL for when modify is called during the execution of the "Hello World" consequence and inspect the Agenda view again. Notice this time we "Debug As" a "Drools application" and not a "Java application".</para>
-
- <orderedlist>
- <listitem>
- <para>Open the class org.drools.examples.FibonacciExample in your Eclipse IDE</para>
- </listitem>
-
- <listitem>
- <para>Right-click the class an select "Debug as..." -> "Drools application"</para>
- </listitem>
- </orderedlist>
-
- <para>Now we can see that the other rule "Good Bye" which uses the java dialect is activated and placed on the agenda.</para>
-
- <figure>
- <title>Hello World : rule "Hello World" Agenda View</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="EX_helloworld_agenda2.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The "Good Bye" rule is similar to the "Hello World" rule but matches Message objects whose status is Message.GOODBYE instead, printing its message to the default console, it specifies the "java" dialect.</para>
-
- <example>
- <title>HelloWorld example: rule "Good Bye"</title>
-
- <programlisting>rule "Good Bye"
- dialect "java"
- when
- Message( status == Message.GOODBYE, message : message )
- then
- System.out.println( message );
-end</programlisting>
- </example>
-
- <para>If you remember at the start of this example in the java code we created a WorkingMemoryFileLogger and called logger.writeToDisk() at the end, this created an audit log file that can be shown in the Audit view. We use the audit view in many of the examples to try and understand the example execution flow. In the view below we can see the object is inserted which creates an activation for the "Hello World" rule, the activation is then executed which updated the Message object causing the "Good Bye" rule to activate, the "Good Bye" rule then also executes. When an event in the Audit view is select it highlights the origin event in green, so below the Activation created event is highlighted in greed as the origin of the Activation executed event.</para>
-
- <figure>
- <title>Hello World : Audit View</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="helloworld_auditview1.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
<section>
- <title>State Example</title>
-
- <para>This example is actually implemented in three different versions to demonstrate different ways of implementing the same basic behavior: rules forward chaining, i.e., the ability the engine has to evaluate, activate and fire rules in sequence, based on changes on the facts in the working memory.</para>
-
- <section>
- <title>Understanding the State Example</title>
-
- <screen><emphasis role="bold">Name:</emphasis> State Example
-<emphasis role="bold">Main class:</emphasis> org.drools.examples.StateExampleUsingSalience
-<emphasis role="bold">Type:</emphasis> java application
-<emphasis role="bold">Rules file:</emphasis> StateExampleUsingSalience.drl
-<emphasis role="bold">Objective:</emphasis> Demonstrates basic rule use and Conflict Resolution for rule firing priority.</screen>
-
- <para>Each State class has fields for its name and its current state (see org.drools.examples.State class). The two possible states for each objects are:</para>
-
- <itemizedlist>
- <listitem>
- <para>NOTRUN</para>
- </listitem>
-
- <listitem>
- <para>FINISHED</para>
- </listitem>
- </itemizedlist>
-
- <example>
- <title>State Class</title>
-
- <programlisting>public class State {
- public static final int NOTRUN = 0;
- public static final int FINISHED = 1;
-
- private final PropertyChangeSupport changes = new PropertyChangeSupport( this );
-
- private String name;
- private int state;
-
- ... setters and getters go here...
-}</programlisting>
- </example>
-
- <para>Ignore the PropertyChangeSupport for now, that will be explained later. In the example we create four State objects with names: A, B, C and D. Initially all are set to state NOTRUN, which is default for the used constructor. Each instance is asserted in turn into the session and then fireAllRules() is called.</para>
-
- <example>
- <title>Salience State Example Execution</title>
-
- <programlisting>State a = new State( "A" );
-State b = new State( "B" );
-State c = new State( "C" );
-final State d = new State( "D" );
-
-// By setting dynamic to TRUE, Drools will use JavaBean
-// PropertyChangeListeners so you don't have to call update().
-boolean dynamic = true;
-
-session.insert( a,
- dynamic );
-session.insert( b,
- dynamic );
-session.insert( c,
- dynamic );
-session.insert( d,
- dynamic );
-
-session.fireAllRules();
-session.dispose(); // Stateful rule session must always be disposed when finished</programlisting>
- </example>
-
- <para>To execute the application:</para>
-
- <orderedlist>
- <listitem>
- <para>Open the class org.drools.examples.StateExampleUsingSalience in your Eclipse IDE</para>
- </listitem>
-
- <listitem>
- <para>Right-click the class an select "Run as..." -> "Java application"</para>
- </listitem>
- </orderedlist>
-
- <para>And you will see the following output in the Eclipse console output:</para>
-
- <example>
- <title>Salience State Example Console Output</title>
-
- <programlisting>A finished
-B finished
-C finished
-D finished
-</programlisting>
- </example>
-
- <para>There are four rules in total, first a Bootstrap rule fires setting A to state FINISHED which then causes B to change to state FINISHED. C and D are both dependent on B - causing a conflict which is resolved by setting salience values. First lets look at how this was executed</para>
-
- <para>The best way to understand what is happening is to use the "Audit Log" feature to graphically see the results of each operation. The Audit log was generated when the example was previously run. To view the Audit log in Eclipse:</para>
-
- <orderedlist>
- <listitem>
- <para>If the "Audit View" is not visible, click on: "Window"->"Show View"->"Other..."->"Drools"->"Audit View"</para>
- </listitem>
-
- <listitem>
- <para>In the "Audit View" click in the "Open Log" button and select the file "<drools-examples-drl-dir>/log/state.log"</para>
- </listitem>
- </orderedlist>
-
- <para>After that, the "Audit view" will look like the following screenshot.</para>
-
- <figure>
- <title>Salience State Example Audit View</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="state_example_audit1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Reading the log in the "Audit View", top to down, we see every action and the corresponding changes in the working memory. This way we see that the assertion of the State "A" object with the "NOTRUN" state activates the "Bootstrap" rule, while the assertions of the other state objects have no immediate effect.</para>
-
- <example>
- <title>Salience State Example: Rule "Bootstrap"</title>
-
- <programlisting>rule Bootstrap
- when
- a : State(name == "A", state == State.NOTRUN )
- then
- System.out.println(a.getName() + " finished" );
- a.setState( State.FINISHED );
-end</programlisting>
- </example>
-
- <para>The execution of "Bootstrap" rule changes the state of "A" to "FINISHED", that in turn activates the "A to B" rule.</para>
-
- <example>
- <title>Salience State Example: Rule "A to B"</title>
-
- <programlisting>rule "A to B"
- when
- State(name == "A", state == State.FINISHED )
- b : State(name == "B", state == State.NOTRUN )
- then
- System.out.println(b.getName() + " finished" );
- b.setState( State.FINISHED );
-end
-</programlisting>
- </example>
-
- <para>The execution of "A to B" rule changes the state of "B" to "FINISHED", which activates both rules "B to C" and "B to D", placing both Activations onto the Agenda. In this moment the two rules may fire and are said to be in conflict. The conflict resolution strategy allows the engine's Agenda to decide which rule to fire. As the "B to C" rule has a <emphasis role="bold">higher salience value</emphasis> (10 versus the default salience value of 0), it fires first, modifying the "C" object to state "FINISHED". The Audit view above shows the modification of the State object in the rule "A to B" which results in two highlighted activations being in conflict. The Agenda view can also be used to investigate the state of the Agenda, debug points can be placed in the rules themselves and the Agenda view opened; the screen shot below shows the break point in the rule "A to B" and the state of the Agenda with the two conflicting rules.</para>
-
- <figure>
- <title>State Example Agenda View</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="state_example_agenda1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <example>
- <title>Salience State Example: Rule "B to C"</title>
-
- <programlisting>rule "B to C"
- salience 10
- when
- State(name == "B", state == State.FINISHED )
- c : State(name == "C", state == State.NOTRUN )
- then
- System.out.println(c.getName() + " finished" );
- c.setState( State.FINISHED );
-end
-</programlisting>
- </example>
-
- <para>The "B to D" rule fires last, modifying the "D" object to state "FINISHED".</para>
-
- <example>
- <title>Salience State Example: Rule "B to D"</title>
-
- <programlisting>rule "B to D"
- when
- State(name == "B", state == State.FINISHED )
- d : State(name == "D", state == State.NOTRUN )
- then
- System.out.println(d.getName() + " finished" );
- d.setState( State.FINISHED );
-end</programlisting>
- </example>
-
- <para>There are no more rules to execute and so the engine stops.</para>
-
- <para>Another notable concept in this example is the use of <emphasis role="bold">dynamic facts</emphasis>, which is the PropertyChangeListener part. As mentioned previously in the documentation, in order for the engine to see and react to fact's properties change, the application must tell the engine that changes occurred. This can be done explicitly in the rules, by calling the <emphasis role="bold">update()</emphasis> memory action, or implicitly by letting the engine know that the facts implement PropertyChangeSupport as defined by the <emphasis>Javabeans specification</emphasis>. This example demonstrates how to use PropertyChangeSupport to avoid the need for explicit update() calls in the rules. To make use of this feature, make sure your facts implement the PropertyChangeSupport as the org.drools.example.State class does and use the following code to insert the facts into the working memory:</para>
-
- <example>
- <title>Inserting a Dynamic Fact</title>
-
- <programlisting>// By setting dynamic to TRUE, Drools will use JavaBean
-// PropertyChangeListeners so you don't have to call update().
-final boolean dynamic = true;
-
-session.insert( fact,
- dynamic );
-</programlisting>
- </example>
-
- <para>When using PropertyChangeListeners each setter must implement a little extra code to do the notification, here is the state setter for thte org.drools.examples.State class:</para>
-
- <example>
- <title>Setter Example with PropertyChangeSupport</title>
-
- <programlisting>public void setState(final int newState) {
- int oldState = this.state;
- this.state = newState;
- this.changes.firePropertyChange( "state",
- oldState,
- newState );
-}</programlisting>
- </example>
-
- <para>There are two other State examples: StateExampleUsingAgendGroup and StateExampleWithDynamicRules. Both execute from A to B to C to D, as just shown, the StateExampleUsingAgendGroup uses agenda-groups to control the rule conflict and which one fires first and StateExampleWithDynamicRules shows how an additional rule can be added to an already running WorkingMemory with all the existing data applying to it at runtime.</para>
-
- <para>Agenda groups are a way to partition the agenda into groups and controlling which groups can execute. All rules by default are in the "MAIN" agenda group, by simply using the "agenda-group" attribute you specify a different agenda group for the rule. A working memory initially only has focus on the "MAIN" agenda group, only when other groups are given the focus can their rules fire; this can be achieved by either using the method setFocus() or the rule attribute "auto-focus". "auto-focus" means that the rule automatically sets the focus to it's agenda group when the rule is matched and activated. It is this "auto-focus" that enables "B to C" to fire before "B to D".</para>
-
- <example>
- <title>Agenda Group State Example: Rule "B to C"</title>
-
- <programlisting>rule "B to C"
- agenda-group "B to C"
- auto-focus true
- when
- State(name == "B", state == State.FINISHED )
- c : State(name == "C", state == State.NOTRUN )
- then
- System.out.println(c.getName() + " finished" );
- c.setState( State.FINISHED );
- drools.setFocus( "B to D" );
-end</programlisting>
- </example>
-
- <para>The rule "B to C" calls "drools.setFocus( "B to D" );" which gives the agenda group "B to D" focus allowing its active rules to fire; which allows the rule "B to D" to fire.</para>
-
- <example>
- <title>Agenda Group State Example: Rule "B to D"</title>
-
- <programlisting>rule "B to D"
- agenda-group "B to D"
- when
- State(name == "B", state == State.FINISHED )
- d : State(name == "D", state == State.NOTRUN )
- then
- System.out.println(d.getName() + " finished" );
- d.setState( State.FINISHED );
-end</programlisting>
- </example>
-
- <para>The example StateExampleWithDynamicRules adds another rule to the RuleBase after fireAllRules(), the rule it adds is just another State transition.</para>
-
- <example>
- <title>Dynamic State Example: Rule "D to E"</title>
-
- <programlisting>rule "D to E"
- when
- State(name == "D", state == State.FINISHED )
- e : State(name == "E", state == State.NOTRUN )
- then
- System.out.println(e.getName() + " finished" );
- e.setState( State.FINISHED );
-end</programlisting>
- </example>
-
- <para>It gives the following expected output:</para>
-
- <example>
- <title>Dynamic Sate Example Output</title>
-
- <programlisting>A finished
-B finished
-C finished
-D finished
-E finished
-</programlisting>
- </example>
-
- </section>
-
- </section>
-
- <section>
- <title>Banking Tutorial</title>
-
- <screen><emphasis role="bold">Name:</emphasis> BankingTutorial
-<emphasis role="bold">Main class:</emphasis> org.drools.tutorials.banking.*
-<emphasis role="bold">Type:</emphasis> java application
-<emphasis role="bold">Rules file:</emphasis> org.drools.tutorials.banking.*
-<emphasis role="bold">Objective:</emphasis> tutorial that builds up knowledge of pattern matching, basic sorting and calculation rules.</screen>
-
- <para>This tutorial will demonstrate the process of developing a complete personal banking application that will handle credits, debits, currencies and that will use a set of design patterns that have been created for the process. In order to make the examples documented here clear and modular, I will try and steer away from re-visiting existing code to add new functionality, and will instead extend and inject where appropriate.</para>
-
- <para>The RuleRunner class is a simple harness to execute one or more drls against a set of data. It compiles the Packages and creates the RuleBase for each execution, this allows us to easy execute each scenario and see the outputs. In reality this is not a good solution for a production system where the RuleBase should be built just once and cached, but for the purposes of this tutorial it shall suffice.</para>
-
- <example>
- <title>Banking Tutorial : RuleRunner</title>
-
- <programlisting>public class RuleRunner {
-
- public RuleRunner() {
- }
-
- public void runRules(String[] rules,
- Object[] facts) throws Exception {
-
- RuleBase ruleBase = RuleBaseFactory.newRuleBase();
- PackageBuilder builder = new PackageBuilder();
-
- for ( int i = 0; i < rules.length; i++ ) {
- String ruleFile = rules[i];
- System.out.println( "Loading file: " + ruleFile );
- builder.addPackageFromDrl(new InputStreamReader( RuleRunner.class.getResourceAsStream( ruleFile ) ) );
- }
-
- Package pkg = builder.getPackage();
- ruleBase.addPackage( pkg );
- WorkingMemory workingMemory = ruleBase.newStatefulSession();
-
- for ( int i = 0; i < facts.length; i++ ) {
- Object fact = facts[i];
- System.out.println( "Inserting fact: " + fact );
- workingMemory.insert( fact );
- }
-
- workingMemory.fireAllRules();
- }
-}</programlisting>
- </example>
-
- <para>This is our first Example1.java class it loads and executes a single drl file "Example.drl" but inserts no data.</para>
-
- <example>
- <title>Banking Tutorial : Java Example1</title>
-
- <programlisting>public class Example1 {
- public static void main(String[] args) throws Exception {
- new RuleRunner().runRules( new String[] { "Example1.drl" },
- new Object[0] );
- }
-}</programlisting>
- </example>
-
- <para>And this is the first simple rule to execute. It has a single "eval" condition that will alway be true, thus this rul will always match and fire.</para>
-
- <example>
- <title>Banking Tutorial : Rule Example1</title>
-
- <programlisting>rule "Rule 01"
- when
- eval (1==1)
- then
- System.out.println("Rule 01 Works");
-endh</programlisting>
- </example>
-
- <para>The output for the rule is below, the rule matches and executes the single print statement.</para>
-
- <example>
- <title>Banking Tutorial : Output Example1</title>
-
- <programlisting>Loading file: Example1.drl
-Rule 01 Works</programlisting>
- </example>
-
- <para>The next step is to assert some simple facts and print them out. </para>
-
- <example>
- <title>Banking Tutorial : Java Example2</title>
-
- <programlisting>public class Example2 {
- public static void main(String[] args) throws Exception {
- Number[] numbers = new Number[] {wrap(3), wrap(1), wrap(4), wrap(1), wrap(5)};
- new RuleRunner().runRules( new String[] { "Example2.drl" },
- numbers );
- }
-
- private static Integer wrap(int i) {
- return new Integer(i);
- }
-}</programlisting>
- </example>
-
- <para>This doesn’t use any specific facts but instead asserts a set of java.lang.Integer’s. This is not considered "best practice" as a number of a collection is not a fact, it is not a thing. A Bank acount has a number, its balance, thus the Account is the fact; but to get started asserting Integers shall suffice for demonstration purposes as the complexity is built up.</para>
-
- <para>Now we will create a simple rule to print out these numbers.</para>
-
- <example>
- <title>Banking Tutorial : Rule Example2</title>
-
- <programlisting>rule "Rule 02"
- when
- Number( $intValue : intValue )
- then
- System.out.println("Number found with value: " + $intValue);
-end</programlisting>
- </example>
-
- <para>Once again, this rule does nothing special. It identifies any facts that are Numbers and prints out the values. Notice the user of interfaces here, we inserted Integers but the pattern matching engine is able to match the interfaces and super classes of the asserted objects.</para>
-
- <para>The output shows the drl being loaded, the facts inserted and then the matched and fired rules. We can see that each inserted number is matched and fired and thus printed.</para>
-
- <example>
- <title>Banking Tutorial : Output Example2</title>
-
- <programlisting>Loading file: Example2.drl
-Inserting fact: 3
-Inserting fact: 1
-Inserting fact: 4
-Inserting fact: 1
-Inserting fact: 5
-Number found with value: 5
-Number found with value: 1
-Number found with value: 4
-Number found with value: 1
-Number found with value: 3
-</programlisting>
- </example>
-
- <para>here are probably a hundred and one better ways to sort numbers; but we will need to apply some cashflows in date order when we start looking at banking rules so let’s look at a simple rule based example.</para>
-
- <example>
- <title>Banking Tutorial : Java Example3</title>
-
- <programlisting>public class Example3 {
- public static void main(String[] args) throws Exception {
- Number[] numbers = new Number[] {wrap(3), wrap(1), wrap(4), wrap(1), wrap(5)};
- new RuleRunner().runRules( new String[] { "Example3.drl" },
- numbers );
- }
-
- private static Integer wrap(int i) {
- return new Integer(i);
- }
-}</programlisting>
- </example>
-
- <para>Again we insert our Integers as before, this time the rule is slightly different:</para>
-
- <example>
- <title>Banking Tutorial : Rule Example3</title>
-
- <programlisting>rule "Rule 03"
- when
- $number : Number( )
- not Number( intValue < $number.intValue )
- then
- System.out.println("Number found with value: " + $number.intValue() );
- retract( $number );
-end</programlisting>
- </example>
-
- <para>The first line of the rules identifies a Number and extracts the value. The second line ensures that there does not exist a smaller number than the one found. By executing this rule, we might expect to find only one number - the smallest in the set. However, the retraction of the number after it has been printed, means that the smallest number has been removed, revealing the next smallest number, and so on. </para>
-
- <para>So, the output we generate is, notice the numbers are now sorted numerically.</para>
-
- <example>
- <title>Banking Tutorial : Output Example3</title>
-
- <programlisting>Loading file: Example3.drl
-Inserting fact: 3
-Inserting fact: 1
-Inserting fact: 4
-Inserting fact: 1
-Inserting fact: 5
-Number found with value: 1
-Number found with value: 1
-Number found with value: 3
-Number found with value: 4
-Number found with value: 5
-</programlisting>
- </example>
-
- <para>Now we want to start moving towards our personal accounting rules. The first step is to create a Cashflow POJO.</para>
-
- <example>
- <title>Banking Tutoria : Class Cashflow</title>
-
- <programlisting>public class Cashflow {
- private Date date;
- private double amount;
-
- public Cashflow() {
- }
-
- public Cashflow(Date date,
- double amount) {
- this.date = date;
- this.amount = amount;
- }
-
- public Date getDate() {
- return date;
- }
-
- public void setDate(Date date) {
- this.date = date;
- }
-
- public double getAmount() {
- return amount;
- }
-
- public void setAmount(double amount) {
- this.amount = amount;
- }
-
- public String toString() {
- return "Cashflow[date=" + date + ",amount=" + amount + "]";
- }
-}</programlisting>
- </example>
-
- <para>The Cashflow has two simple attributes, a date and an amount. I have added a toString method to print it and overloaded the constructor to set the values. The Example4 java code inserts 5 Cashflow objecst with varying dates and amounts.</para>
-
- <example>
- <title>Banking Tutorial : Java Example4</title>
-
- <programlisting>public class Example4 {
- public static void main(String[] args) throws Exception {
- Object[] cashflows = {
- new Cashflow(new SimpleDate("01/01/2007"), 300.00),
- new Cashflow(new SimpleDate("05/01/2007"), 100.00),
- new Cashflow(new SimpleDate("11/01/2007"), 500.00),
- new Cashflow(new SimpleDate("07/01/2007"), 800.00),
- new Cashflow(new SimpleDate("02/01/2007"), 400.00),
- };
-
- new RuleRunner().runRules( new String[] { "Example4.drl" },
- cashflows );
- }
-}</programlisting>
- </example>
-
- <para>SimpleDate is a simple class that extends Date and takes a String as input. It allows for pre-formatted Data classes, for convienience. The code is listed below</para>
-
- <example>
- <title>Banking Tutorial : Java SimpleDate</title>
-
- <programlisting>public class SimpleDate extends Date {
- private static final SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
-
- public SimpleDate(String datestr) throws Exception {
- setTime(format.parse(datestr).getTime());
- }
-}</programlisting>
- </example>
-
- <para>Now, let’s look at rule04.drl to see how we print the sorted Cashflows:</para>
-
- <example>
- <title>Banking Tutorial : Rule Example4</title>
-
- <programlisting>rule "Rule 04"
- when
- $cashflow : Cashflow( $date : date, $amount : amount )
- not Cashflow( date < $date)
- then
- System.out.println("Cashflow: "+$date+" :: "+$amount);
- retract($cashflow);
-end</programlisting>
- </example>
-
- <para>Here, we identify a Cashflow and extract the date and the amount. In the second line of the rules we ensure that there is not a Cashflow with an earlier date than the one found. In the consequences, we print the Cashflow that satisfies the rules and then retract it, making way for the next earliest Cashflow. So, the output we generate is:</para>
-
- <example>
- <title>Banking Tutorial : Output Example4</title>
-
- <programlisting>Loading file: Example4.drl
-Inserting fact: Cashflow[date=Mon Jan 01 00:00:00 GMT 2007,amount=300.0]
-Inserting fact: Cashflow[date=Fri Jan 05 00:00:00 GMT 2007,amount=100.0]
-Inserting fact: Cashflow[date=Thu Jan 11 00:00:00 GMT 2007,amount=500.0]
-Inserting fact: Cashflow[date=Sun Jan 07 00:00:00 GMT 2007,amount=800.0]
-Inserting fact: Cashflow[date=Tue Jan 02 00:00:00 GMT 2007,amount=400.0]
-Cashflow: Mon Jan 01 00:00:00 GMT 2007 :: 300.0
-Cashflow: Tue Jan 02 00:00:00 GMT 2007 :: 400.0
-Cashflow: Fri Jan 05 00:00:00 GMT 2007 :: 100.0
-Cashflow: Sun Jan 07 00:00:00 GMT 2007 :: 800.0
-Cashflow: Thu Jan 11 00:00:00 GMT 2007 :: 500.0
-</programlisting>
- </example>
-
- <para>Here we extend our Cashflow to give a TypedCashflow which can be CREDIT or DEBIT. Ideally, we would just add this to the Cashflow type, but so that we can keep all the examples simple, we will go with the extensions.</para>
-
- <example>
- <title>Banking Tutoria : Class TypedCashflow</title>
-
- <programlisting>public class TypedCashflow extends Cashflow {
- public static final int CREDIT = 0;
- public static final int DEBIT = 1;
-
- private int type;
-
- public TypedCashflow() {
- }
-
- public TypedCashflow(Date date,
- int type,
- double amount) {
- super( date,
- amount );
- this.type = type;
- }
-
- public int getType() {
- return type;
- }
-
- public void setType(int type) {
- this.type = type;
- }
-
- public String toString() {
- return "TypedCashflow[date=" + getDate() + ",type=" + (type == CREDIT ? "Credit" : "Debit") + ",amount=" + getAmount() + "]";
- }
-}</programlisting>
- </example>
-
- <para>There are lots of ways to improve this code, but for the sake of the example this will do.</para>
-
- <para>Nows lets create the Example5 runner.</para>
-
- <example>
- <title>Banking Tutorial : Java Example5</title>
-
- <programlisting>public class Example5 {
- public static void main(String[] args) throws Exception {
- Object[] cashflows = {
- new TypedCashflow(new SimpleDate("01/01/2007"),
- TypedCashflow.CREDIT, 300.00),
- new TypedCashflow(new SimpleDate("05/01/2007"),
- TypedCashflow.CREDIT, 100.00),
- new TypedCashflow(new SimpleDate("11/01/2007"),
- TypedCashflow.CREDIT, 500.00),
- new TypedCashflow(new SimpleDate("07/01/2007"),
- TypedCashflow.DEBIT, 800.00),
- new TypedCashflow(new SimpleDate("02/01/2007"),
- TypedCashflow.DEBIT, 400.00),
- };
-
- new RuleRunner().runRules( new String[] { "Example5.drl" },
- cashflows );
- }
-}</programlisting>
- </example>
-
- <para>Here, we simply create a set of Cashflows which are either CREDIT or DEBIT Cashflows and supply them and rule05.drl to the RuleEngine. </para>
-
- <para>Now, let’s look at rule0 Example5.drl to see how we print the sorted Cashflows:</para>
-
- <example>
- <title>Banking Tutorial : Rule Example5</title>
-
- <programlisting>rule "Rule 05"
- when
- $cashflow : TypedCashflow( $date : date,
- $amount : amount,
- type == TypedCashflow.CREDIT )
- not TypedCashflow( date < $date,
- type == TypedCashflow.CREDIT )
- then
- System.out.println("Credit: "+$date+" :: "+$amount);
- retract($cashflow);
-end</programlisting>
- </example>
-
- <para>Here, we identify a Cashflow with a type of CREDIT and extract the date and the amount. In the second line of the rules we ensure that there is not a Cashflow of type CREDIT with an earlier date than the one found. In the consequences, we print the Cashflow that satisfies the rules and then retract it, making way for the next earliest Cashflow of type CREDIT.</para>
-
- <para>So, the output we generate is</para>
-
- <example>
- <title>Banking Tutorial : Output Example5</title>
-
- <screen>Loading file: Example5.drl
-Inserting fact: TypedCashflow[date=Mon Jan 01 00:00:00 GMT 2007,type=Credit,amount=300.0]
-Inserting fact: TypedCashflow[date=Fri Jan 05 00:00:00 GMT 2007,type=Credit,amount=100.0]
-Inserting fact: TypedCashflow[date=Thu Jan 11 00:00:00 GMT 2007,type=Credit,amount=500.0]
-Inserting fact: TypedCashflow[date=Sun Jan 07 00:00:00 GMT 2007,type=Debit,amount=800.0]
-Inserting fact: TypedCashflow[date=Tue Jan 02 00:00:00 GMT 2007,type=Debit,amount=400.0]
-Credit: Mon Jan 01 00:00:00 GMT 2007 :: 300.0
-Credit: Fri Jan 05 00:00:00 GMT 2007 :: 100.0
-Credit: Thu Jan 11 00:00:00 GMT 2007 :: 500.0
-</screen>
- </example>
-
- <para>Here we are going to process both CREDITs and DEBITs on 2 bank accounts to calculate the account balance. In order to do this, I am going to create two separate Account Objects and inject them into the Cashflows before passing them to the Rule Engine. The reason for this is to provide easy access to the correct Bank Accounts without having to resort to Helper classes. Let’s take a look at the Account class first. This is a simple POJO with an account number and balance:</para>
-
- <example>
- <title>Banking Tutoria : Class Account</title>
-
- <programlisting>public class Account {
- private long accountNo;
- private double balance = 0;
-
- public Account() {
- }
-
- public Account(long accountNo) {
- this.accountNo = accountNo;
- }
-
- public long getAccountNo() {
- return accountNo;
- }
-
- public void setAccountNo(long accountNo) {
- this.accountNo = accountNo;
- }
-
- public double getBalance() {
- return balance;
- }
-
- public void setBalance(double balance) {
- this.balance = balance;
- }
-
- public String toString() {
- return "Account[" + "accountNo=" + accountNo + ",balance=" + balance + "]";
- }
-}</programlisting>
- </example>
-
- <para>Now let’s extend our TypedCashflow to give AllocatedCashflow (allocated to an account).</para>
-
- <example>
- <title>Banking Tutoria : Class AllocatedCashflow</title>
-
- <programlisting>public class AllocatedCashflow extends TypedCashflow {
- private Account account;
-
- public AllocatedCashflow() {
- }
-
- public AllocatedCashflow(Account account,
- Date date,
- int type,
- double amount) {
- super( date,
- type,
- amount );
- this.account = account;
- }
-
- public Account getAccount() {
- return account;
- }
-
- public void setAccount(Account account) {
- this.account = account;
- }
-
- public String toString() {
- return "AllocatedCashflow[" + "account=" + account + ",date=" + getDate() +
- ",type=" + (getType() == CREDIT ? "Credit" : "Debit") +
- ",amount=" + getAmount() + "]";
- }
-}</programlisting>
- </example>
-
- <para>Now, let’s java code for Example5 execution. Here we create two Account objects and inject one into each cashflow as appropriate. For simplicity I have simply included them in the constructor.</para>
-
- <example>
- <title>Banking Tutorial : Java Example5</title>
-
- <programlisting>public class Example6 {
- public static void main(String[] args) throws Exception {
- Account acc1 = new Account(1);
- Account acc2 = new Account(2);
-
- Object[] cashflows = {
- new AllocatedCashflow(acc1,new SimpleDate("01/01/2007"),
- TypedCashflow.CREDIT, 300.00),
- new AllocatedCashflow(acc1,new SimpleDate("05/02/2007"),
- TypedCashflow.CREDIT, 100.00),
- new AllocatedCashflow(acc2,new SimpleDate("11/03/2007"),
- TypedCashflow.CREDIT, 500.00),
- new AllocatedCashflow(acc1,new SimpleDate("07/02/2007"),
- TypedCashflow.DEBIT, 800.00),
- new AllocatedCashflow(acc2,new SimpleDate("02/03/2007"),
- TypedCashflow.DEBIT, 400.00),
- new AllocatedCashflow(acc1,new SimpleDate("01/04/2007"),
- TypedCashflow.CREDIT, 200.00),
- new AllocatedCashflow(acc1,new SimpleDate("05/04/2007"),
- TypedCashflow.CREDIT, 300.00),
- new AllocatedCashflow(acc2,new SimpleDate("11/05/2007"),
- TypedCashflow.CREDIT, 700.00),
- new AllocatedCashflow(acc1,new SimpleDate("07/05/2007"),
- TypedCashflow.DEBIT, 900.00),
- new AllocatedCashflow(acc2,new SimpleDate("02/05/2007"),
- TypedCashflow.DEBIT, 100.00)
- };
-
- new RuleRunner().runRules( new String[] { "Example6.drl" },
- cashflows );
- }
-}</programlisting>
- </example>
-
- <para>Now, let’s look at rule Example06.drl to see how we apply each cashflow in date order and calculate and print the balance. </para>
-
- <example>
- <title>Banking Tutorial : Rule Example6</title>
-
- <programlisting>rule "Rule 06 - Credit"
- when
- $cashflow : AllocatedCashflow( $account : account,
- $date : date, $amount : amount,
- type==TypedCashflow.CREDIT )
- not AllocatedCashflow( account == $account, date < $date)
- then
- System.out.println("Credit: " + $date + " :: " + $amount);
- $account.setBalance($account.getBalance()+$amount);
- System.out.println("Account: " + $account.getAccountNo() +
- " - new balance: " + $account.getBalance());
- retract($cashflow);
-end
-
-rule "Rule 06 - Debit"
- when
- $cashflow : AllocatedCashflow( $account : account,
- $date : date, $amount : amount,
- type==TypedCashflow.DEBIT )
- not AllocatedCashflow( account == $account, date < $date)
- then
- System.out.println("Debit: " + $date + " :: " + $amount);
- $account.setBalance($account.getBalance() - $amount);
- System.out.println("Account: " + $account.getAccountNo() +
- " - new balance: " + $account.getBalance());
- retract($cashflow);
-end</programlisting>
- </example>
-
- <para>Here, we have separate rules for CREDITs and DEBITs, however we do not specify a type when checking for earlier cashflows. This is so that all cashflows are applied in date order regardless of which type of cashflow type they are. In the rule section we identify the correct account to work with and in the consequences we update it with the cashflow amount.</para>
-
- <example>
- <title>Banking Tutorial : Output Example6</title>
-
- <programlisting>Loading file: Example6.drl
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Mon Jan 01 00:00:00 GMT 2007,type=Credit,amount=300.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Mon Feb 05 00:00:00 GMT 2007,type=Credit,amount=100.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=2,balance=0.0],date=Sun Mar 11 00:00:00 GMT 2007,type=Credit,amount=500.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Wed Feb 07 00:00:00 GMT 2007,type=Debit,amount=800.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=2,balance=0.0],date=Fri Mar 02 00:00:00 GMT 2007,type=Debit,amount=400.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Sun Apr 01 00:00:00 BST 2007,type=Credit,amount=200.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Thu Apr 05 00:00:00 BST 2007,type=Credit,amount=300.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=2,balance=0.0],date=Fri May 11 00:00:00 BST 2007,type=Credit,amount=700.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=1,balance=0.0],date=Mon May 07 00:00:00 BST 2007,type=Debit,amount=900.0]
-Inserting fact: AllocatedCashflow[account=Account[accountNo=2,balance=0.0],date=Wed May 02 00:00:00 BST 2007,type=Debit,amount=100.0]
-Debit: Fri Mar 02 00:00:00 GMT 2007 :: 400.0
-Account: 2 - new balance: -400.0
-Credit: Sun Mar 11 00:00:00 GMT 2007 :: 500.0
-Account: 2 - new balance: 100.0
-Debit: Wed May 02 00:00:00 BST 2007 :: 100.0
-Account: 2 - new balance: 0.0
-Credit: Fri May 11 00:00:00 BST 2007 :: 700.0
-Account: 2 - new balance: 700.0
-Credit: Mon Jan 01 00:00:00 GMT 2007 :: 300.0
-Account: 1 - new balance: 300.0
-Credit: Mon Feb 05 00:00:00 GMT 2007 :: 100.0
-Account: 1 - new balance: 400.0
-Debit: Wed Feb 07 00:00:00 GMT 2007 :: 800.0
-Account: 1 - new balance: -400.0
-Credit: Sun Apr 01 00:00:00 BST 2007 :: 200.0
-Account: 1 - new balance: -200.0
-Credit: Thu Apr 05 00:00:00 BST 2007 :: 300.0
-Account: 1 - new balance: 100.0
-Debit: Mon May 07 00:00:00 BST 2007 :: 900.0
-Account: 1 - new balance: -800.0
-</programlisting>
- </example>
-
- </section>
-
- <section>
- <title>Fibonacci Example</title>
-
- <screen><emphasis role="bold">Name:</emphasis> Fibonacci
-<emphasis role="bold">Main class:</emphasis> org.drools.examples.FibonacciExample
-<emphasis role="bold">Type:</emphasis> java application
-<emphasis role="bold">Rules file:</emphasis> Fibonacci.drl
-<emphasis role="bold">Objective:</emphasis> Demonsrates Recursion, 'not' CEs and Cross Product Matching</screen>
-
- <para>The Fibonacci Numbers, <ulink url="http://en.wikipedia.org/wiki/Fibonacci_number">http://en.wikipedia.org/wiki/Fibonacci_number</ulink>, invented by Leonardo of Pisa, <ulink url="http://en.wikipedia.org/wiki/Fibonacci">http://en.wikipedia.org/wiki/Fibonacci</ulink>, are obtained by starting with 0 and 1, and then produce the next Fibonacci number by adding the two previous Fibonacci numbers. The first Fibonacci numbers for n = 0, 1,... are: * 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610, 987, 1597, 2584, 4181, 6765, 10946... The Fibonacci Example demonstrates recursion and conflict resolution with Salience values.</para>
-
- <para>A single fact Class is used in this example, Fibonacci. It has two fields, sequence and value. The sequence field is used to indicate the position of the object in the Fibonacci number sequence and the value field shows the value of that Fibonacci object for that sequence position.</para>
-
- <example>
- <title>Fibonacci Class</title>
-
- <programlisting>public static class Fibonacci {
- private int sequence;
- private long value;
-
- ... setters and getters go here...
-}</programlisting>
- </example>
-
- <para>Execute the example:</para>
-
- <orderedlist>
- <listitem>
- <para>Open the class <classname>org.drools.examples.FibonacciExample</classname> in your Eclipse IDE</para>
- </listitem>
-
- <listitem>
- <para>Right-click the class an select "Run as..." -> "Java application"</para>
- </listitem>
- </orderedlist>
-
- <para>And Eclipse shows the following output in its console, "...snip..." shows repeated bits removed to save space:</para>
-
- <example>
- <title>Fibonacci Example Console Output</title>
-
- <programlisting>recurse for 50
-recurse for 49
-recurse for 48
-recurse for 47
-...snip...
-recurse for 5
-recurse for 4
-recurse for 3
-recurse for 2
-1 == 1
-2 == 1
-3 == 2
-4 == 3
-5 == 5
-6 == 8
-...snip...
-47 == 2971215073
-48 == 4807526976
-49 == 7778742049
-50 == 12586269025
-</programlisting>
- </example>
-
- <para>To kick this off from java we only insert a single Fibonacci object, with a sequence of 50, a recurse rule is then used to insert the other 49 Fibonacci objects. This example doesn't use PropertyChangeSupport and uses the MVEL dialect, this means we can use the <emphasis role="bold">modify</emphasis> keyword, which allows a block setter action which also notifies the engine of changes.</para>
-
- <example>
- <title>Fibonacci Example Execution</title>
-
- <programlisting>session.insert( new Fibonacci( 50 ) );
-session.fireAllRules();</programlisting>
- </example>
-
- <para>The recurse rule is very simple, it matches each asserted Fibonacci object with a value of -1, it then creates and asserts a new Fibonacci object with a sequence of one less than the currently matched object. Each time a Fibonacci object is added, as long as one with a "sequence == 1" does not exist, the rule re-matches again and fires; causing the recursion. The 'not' conditional element is used to stop the rule matching once we have all 50 Fibonacci objects in memory. The rule also has a salience value, this is because we need to have all 50 Fibonacci objects asserted before we execute the Bootstrap rule.</para>
-
- <example>
- <title>Fibonacci Example : Rule "Recurse"</title>
-
- <programlisting>rule Recurse
- salience 10
- when
- f : Fibonacci ( value == -1 )
- not ( Fibonacci ( sequence == 1 ) )
- then
- insert( new Fibonacci( f.sequence - 1 ) );
- System.out.println( "recurse for " + f.sequence );
-end</programlisting>
- </example>
-
- <para>The audit view shows the original assertion of the Fibonacci object with a sequence of 50, this was done from Java land. From there the audit view shows the continual recursion of the rule, each asserted Fibonacci causes the "Recurse" rule to become activate again, which then fires.</para>
-
- <figure>
- <title>Fibonacci Example "Recurse" Audit View 1</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="fibonacci1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When a Fibonacci with a sequence of 2 is asserted the "Bootstrap" rule is matched and activated along with the "Recurse" rule.</para>
-
- <example>
- <title>Fibonacci Example : Rule "Bootstrap"</title>
-
- <programlisting>rule Bootstrap
- when
- f : Fibonacci( sequence == 1 || == 2, value == -1 ) // this is a multi-restriction || on a single field
- then
- modify ( f ){ value = 1 };
- System.out.println( f.sequence + " == " + f.value );
-end</programlisting>
- </example>
-
- <para>At this point the Agenda looks like the figure shown below. However the "Bootstrap" rule does not fire as the "Recurse" rule has a higher salience.</para>
-
- <figure>
- <title>Fibonacci Example "Recurse" Agenda View 1</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="fibonacci_agenda1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When a Fibonacci with a sequence of 1 is asserted the "Bootstrap" rule is matched again, causing two activations for this rule; note that the "Recurse" rule does not match and activate because the 'not conditional element stops the rule matching when a Fibonacci with a sequence of 1 exists.</para>
-
- <figure>
- <title>Fibonacci Example "Recurse" Agenda View 2</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="fibonacci_agenda2.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Once we have two Fibonacci objects both with values not equal to -1 the "calculate" rule is able to match; remember it was the "Bootstrap" rule that set the Fibonacci's with sequences 1 and 2 to values of 1. At this point we have 50 Fibonacci objects in the Working Memory and we some how need to select the correct ones to calculate each of their values in turn. With three Fibonacci patterns in a rule with no field constriants to correctly constrain the available cross products we have 50x50x50 possible permutations, thats 125K possible rule firings. The "Calculate" rule uses the field constraints to correctly constraint the thee Fibonacci patterns and in the correct order; this technique is called "cross product matching". The first pattern finds any Fibonacci with a value != -1 and binds both the pattern and the field. The second Fibonacci does too but it adds an additional field constraint to make sure that its sequence is one greater than the Fibonacci bound to f!
1. When this rule first fires we know that only sequences 1 and 2 have values of 1 and the two constraints ensure that f1 references sequence 1 and f2 references sequence2. The final pattern finds the Fibonacci of a value == -1 with a sequence one greater than f2. At this point we have three Fibonacci objects correctly selected from the available cross products and we can do the maths calculating the value for Fibonacci sequence = 3.</para>
-
- <example>
- <title>Fibonacci Example : Rule "Calculate"</title>
-
- <programlisting>rule Calculate
- when
- f1 : Fibonacci( s1 : sequence, value != -1 ) // here we bind sequence
- f2 : Fibonacci( sequence == (s1 + 1 ), value != -1 ) // here we don't, just to demonstrate the different way bindings can be used
- f3 : Fibonacci( s3 : sequence == (f2.sequence + 1 ), value == -1 )
- then
- modify ( f3 ) { value = f1.value + f2.value };
- System.out.println( s3 + " == " + f3.value ); // see how you can access pattern and field bindings
-end
-</programlisting>
- </example>
-
- <para>The MVEL modify keyword updated the value of the Fibonacci object bound to f3, this means we have a new Fibonacci object with a value != -1, this allows the "Calculate" rule to rematch and calculate the next Fibonacci number. The Audit view below shows the how the firing of the last "Bootstrap" modifies the Fibonacci object enabling the "Calculate" rule to match, which then modifies another Fibonacci object allowing the "Calculate" rule to rematch. This continues till the value is set for all Fibonacci objects.</para>
-
- <figure>
- <title>Fibonacci Example "Bootstrap" Audit View 1</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="fibonacci4.png" />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section>
<title>Golfing Example</title>
<screen><emphasis role="bold">Name:</emphasis> Golfing
@@ -4388,8 +3131,7 @@
Insurance Calcule: 0.0
Driver wants non related expenses coverage: 1.05
Driver wants glass coverage: 1.1025
-Driver wants extra assistence: 1.1576250000000001
-Driver wants an extra Car: 1.2155062500000002
+Driver wants extra assistence: 1.1576250000000001Driver wants an extra Car: 1.2155062500000002
Driver Single Young Male Driver factor: 1.9448100000000004
New Licenced driver 2.333772
approve: 0.0
Deleted: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Examples/Thumbs.db
===================================================================
(Binary files differ)
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/master.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/master.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/master.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -112,9 +112,9 @@
<xi:include href="Chapter-Rule_Language/Section-XML.xml" />
</chapter>
- <chapter>
+ <chapter xmlns:xi="http://www.w3.org/2001/XInclude">
<xi:include href="Chapter-Examples/Section-Examples.xml" />
- <chapter>
+ </chapter>
<index/>
</book>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -15,92 +15,4 @@
<name>Drools :: Documentation :: Drools Expert</name>
<description>Drools Expert Documentation</description>
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-flow/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-flow/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-flow/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -14,93 +14,4 @@
<packaging>jdocbook</packaging>
<name>Drools :: Documentation :: Drools Flow</name>
<description>Drools Flow User Guide</description>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-fusion/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-fusion/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-fusion/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -13,94 +13,5 @@
<artifactId>drools-docs-fusion</artifactId>
<packaging>jdocbook</packaging>
<name>Drools :: Documentation :: Drools Fusion</name>
- <description>Drools Fusion User Guide</description>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
+ <description>Drools Fusion User Guide</description>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-guvnor/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-guvnor/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-guvnor/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -14,93 +14,4 @@
<packaging>jdocbook</packaging>
<name>Drools :: Documentation :: Drools Guvnor</name>
<description>Drools Guvnor Documentation</description>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <!--format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format-->
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-solver/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-solver/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-solver/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -15,93 +15,4 @@
<packaging>jdocbook</packaging>
<name>Drools :: Documentation :: Drools Solver</name>
<description>Drools Solver Documentation</description>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-jdocbook-plugin</artifactId>
- <version>2.0.0</version>
- <extensions>true</extensions>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
- </dependency>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
-
- <configuration>
- <sourceDocumentName>master.xml</sourceDocumentName>
- <sourceDirectory>${pom.basedir}/en</sourceDirectory>
- <imageResource>
- <directory>${pom.basedir}/en</directory>
- <excludes>
- <exclude>**/*.xml</exclude>
- </excludes>
- </imageResource>
-
- <!--<cssResource>
- <directory>src/main/css</directory>
- </cssResource>-->
-
- <formats>
- <!--<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>-->
- <format>
- <formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <format>
- <formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format>
- <!--format>
- <formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
- <finalName>index.html</finalName>
- </format-->
- </formats>
-
- <options>
- <xincludeSupported>true</xincludeSupported>
- <xmlTransformerType>saxon</xmlTransformerType>
- <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
- <!-- could also locate the docbook dependency and inspect its version... -->
- <docbookVersion>1.72.0</docbookVersion>
- </options>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <distributionManagement>
- <repository>
- <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
- <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
- <!-- todo : replace this with direct svn access once the svnkit providers are available -->
- <id>repository.jboss.org</id>
- <url>file://${maven.repository.root}</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
-
- <properties>
- <translation>en-US</translation>
- </properties>
</project>
\ No newline at end of file
Modified: labs/jbossrules/trunk/drools-docs/pom.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/pom.xml 2008-06-13 20:32:07 UTC (rev 20475)
+++ labs/jbossrules/trunk/drools-docs/pom.xml 2008-06-13 22:34:41 UTC (rev 20476)
@@ -26,7 +26,7 @@
<dependencies>
<dependency>
<groupId>org.drools</groupId>
- <artifactId>drools-docs-userguide</artifactId>
+ <artifactId>drools-docs-generaluserguide</artifactId>
<version>${project.version}</version>
</dependency>
@@ -67,6 +67,95 @@
</dependency>
</dependencies>
</dependencyManagement>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <version>2.0.0</version>
+ <extensions>true</extensions>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-docbook-xslt</artifactId>
+ <version>1.1.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0</version>
+ <type>jdocbook-style</type>
+ </dependency>
+ </dependencies>
+
+ <configuration>
+ <sourceDocumentName>master.xml</sourceDocumentName>
+ <sourceDirectory>${pom.basedir}/en</sourceDirectory>
+ <imageResource>
+ <directory>${pom.basedir}/en</directory>
+ <excludes>
+ <exclude>**/*.xml</exclude>
+ </excludes>
+ </imageResource>
+
+ <!--<cssResource>
+ <directory>src/main/css</directory>
+ </cssResource>-->
+
+ <formats>
+ <!--<format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <finalName>${pom.name}.pdf</finalName>
+ </format>-->
+ <format>
+ <formatName>html</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>html_single</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>eclipse</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ </formats>
+
+ <options>
+ <xincludeSupported>true</xincludeSupported>
+ <xmlTransformerType>saxon</xmlTransformerType>
+ <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
+ <!-- could also locate the docbook dependency and inspect its version... -->
+ <docbookVersion>1.72.0</docbookVersion>
+ </options>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+
+ <distributionManagement>
+ <repository>
+ <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} -->
+ <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml -->
+ <!-- todo : replace this with direct svn access once the svnkit providers are available -->
+ <id>repository.jboss.org</id>
+ <url>file://${maven.repository.root}</url>
+ </repository>
+ <snapshotRepository>
+ <id>snapshots.jboss.org</id>
+ <name>JBoss Snapshot Repository</name>
+ <url>dav:https://snapshots.jboss.org/maven2</url>
+ </snapshotRepository>
+ </distributionManagement>
+
+ <properties>
+ <translation>en-US</translation>
+ </properties>
</project>
More information about the jboss-svn-commits
mailing list