******************************************
* README FOR ORDERING SERVICE EXAMPLE *
******************************************

The ordering service can be used to show how to use pick instruction and
correlations.
When using the service, you init the transaction, then order as many items 
as you like and finally validate the transaction.

It is similar to online purchasing since you add items to a caddy before 
validating it.
Two timeout can occur:
  - the first one if you are too long to validate your order: the service will
    automatically end 10 minnutes after the session is started
  - the second one if you are too long to order an item: aftr you have started
    a session or ordered an item, you have 2 minutes to order another item or
    to validate the order or else the service will end.

Before running this example, make sure that Orchestra is running.

To use this example, the steps are:
1) deploy the process ('ant deploy')
2) start a session ('ant init')
3) order articles ('ant order'), as many times as you want
4) validate the order ('ant validate')
5) undeploy the process ('ant undeploy')

The command 'ant init' will return at the end of the session ('ant validate' 
or timeout) so you have to use commands 'order' and 'validate' in another 
terminal.

The correlations provide a session behaviour: targets init, order and validate
ask for an id and every requests with the same id belong to the same session.

To see how correlations work, the steps are:
1) deploy the process ('ant deploy')
2) start two session ('ant init') with id 1 and 2
3) order articles ('ant order') for sessions 1 and 2
4) validate the orders ('ant validate') for sessions 1 and 2
5) undeploy the process 
