anchor.diff:                  </xa-datasource>
   ----
   
  +You might have to list the database driver as well, if it's not already there:
  +
  +----
  +                <drivers>
  +                    <driver name="postgresql" module="org.postgresql">
  +                        <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
  +                    </driver>
  +					...
  +                </drivers>
  +----
  +
   === Restart WildFly
   
  -Using your system's scripts or $WF_HOME/bin/standalone.sh
  +Use your system's scripts or $WF_HOME/bin/standalone.sh
   
   === Deploy the app
   
  -cd eedemo-xa
  -
  -mvn wildfly:deploy
  +$ cd eedemo-xa
  +$ mvn wildfly:deploy
   
   === Run it
   
  
positive.code: This uses JPA to commit a distributed transaction
  into two databases, customer and orders, as part of
  a single XA transaction. Or so we hope.
  Requires a full Java EE server, not just Tomcat or Jetty.
  
  == Setup 
  
  You have to do a bit of setup to make this thing work!
  
  === Create the databases
  
  
negative.code: This assumes you have PostgreSQL already running on your computer and configured as a "module"
  in the WildFly server.
  
  Since the point of this app is to demonstrate an XA commit, you have to tell PostgreSQL to allow 
  "prepared transactions". Try setting
  
  max_prepared_transactions = 20
  
  in _postgres.conf_ (wherever that is on your system; to give you a couple of data points,
  on OS X it is /Users/postgres/data/postgresql.conf and on OpenBSD it is 
  /var/postgresql/data/postgresql.conf ).
  
  