Overview:
=========
  Demonstrates the use of the BusinessRulesProcessor which allows for
  modification of the POJOs attached to an ESB Message.  The example uses Rules
  to calculate the discount of an inbound order based on the customer's past 
  history of orders. As such it is an example of a stateful rule service.

  Make sure you have run simple_cbr, transformation_XML2POJO, fun_cbr, and
  business_rules_service quickstarts as their principles are used in this
  more complex example.

Running this quickstart:
========================
  Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
  and a more detailed descripton of the different ways to run the quickstarts.

  A comprehensive description of message transformation can be found in
  ServicesGuide.pdf, located in the docs/services folder.

To Run:
===========================
  1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
  2. Open another command terminal window in this folder ("Window2"), type
     'ant runtest'.
  3. Switch back to Application Server console to see the output from the ESB
  4. In this folder ("Window1"), type 'ant undeploy'.

What to look at in this Quickstart:
===================================
  Look at the jboss-esb.xml and notice how the stateful="true" is set on the 
  BusinessRulesProcessor action of the OrderDiscountService. Review the 
  OrderDiscountOnMultipleOrders.drl file to see how accumulation works. 
  
  Stateful rule services must be told via message properties when to continue with
  the current stateful session and when to dispose of it. This is accomplished via 
  the SetupMessage action based on the orderStatus provided with the inbound XML.

  Because there is no persistence in this example, the customer object created from
  each XML message is actually a different Java object (even though the values are 
  all the same). These are separately inserted into the stateful session, and the
  rules treat them as different objects. A real life implementation would detect
  that the customer already existed, and only insert one customer object into the 
  engine stateful session.
