Overview:
=========
  This Quickstart demonsrates how the BPEL Engine can be used to
  orchestrate business process flow through JBoss ESB.

  It also demonstrates a number of other features of the ESB:
  1. Exposing a Webservice interface for a Service that doesn't have a
     Webservice interface (using the SOAPProcessor action).  In this example,
     the Service being exposed is a legacy EJB based Order Management Service.
  2. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a
     Java interface/typeset that isn't annotated for use with JAXB and how to
     add this config on a JBossWS Webservice endpoint deployment.
  3. Easily transforming a CSV based notification message into a Java object
     that's then used to populate a SOAP request. See next.
  3. Making an invocation on an external Webserivce from within an Action
     Processing Pipeline using the SOAPCleint action.

  See docs folder.

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.

  NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server.  It only runs on the
        JBoss Application Server.
  1. Ensure that the value of the 'directory' attribute on the
     'notificationChannel' (jboss-esb.xml) matches the value of the
     'order.approval.drop.location' property in
     'webservice_esb_bpel/services/order-manager/order-manager.properties',
     and that the directory exists.
  2. Restart your JBoss Application Server.
  3. Goto the BPEL Console (http://localhost:8080/bpel-console) and confirm
     it displays.

To Run:
=======
  1.  In a command terminal window in this folder, type 'ant deploy'.
  2.  Goto 'Processes' on the BPEL Console
      (http://localhost:8080/bpel-console) and confirm that the 'Customer' and
      'OrderProcess' BPEL processes are deployed.
  3.  Start your favorite SOAP client (e.g. SOAPUI) and load the
      'Retailer' WSDL located in the sample's 'bpel/wsdl' folder.
  4.  Load the SOAP client (RetailerBinding/SubmitOrder) with the sample order in
      'bpel/sampleData/customerOrder.xml'.
  5.  Submit the new order using the SOAP UI client.
  6.  View the state of the new process in 'Instances' on the BPEL
      Console.  Will appear as 'RUNNING'. This is because the process is waiting on an
      acknowledgement/notification from the OrderManager service.
  9.  Goto http://localhost:8080/order-manager/
      From here, you can approve the order.
  10. When finished, undeploy the application by typing 'ant undeploy'.
    
