anchor.diff:  
   GlassFish provides EclipseLink as JPA implementation while WildFly provides Hibernate. To be completely implementation independent, your code should reference classes from the package `javax.persistence.*` only. If it happens to reference classes from `org.eclipse.persistence.*`, then your application depends on EclipseLink to work properly, whether you refactor it to use `javax.persistence` classes and smoothly move to Hibernate, or you add EclipseLink as a dependence to the project. In the last case, you can explicitly declare in the `persistence.xml` the use of EclipseLink instead of Hibernate. Add the tag `provider` as illustrated below:
   
  +[source,xml]
  +----
       <persistence-unit name="app-pu" transaction-type="JTA">
           <jta-data-source>java:/jdbc/AppDS</jta-data-source>
           <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
           <exclude-unlisted-classes>false</exclude-unlisted-classes>
           <properties/>
       </persistence-unit>
  +----
   
   Then add the following dependence to your `pom.xml` file:
   
  +[source,xml]
  +----
       <dependency>
           <groupId>org.eclipse.persistence</groupId>
           <artifactId>eclipselink</artifactId>
           <version>2.5.1</version>
       </dependency>
  +----
   
   You can find a complete list of Java EE implementations provided by WildFly on this http://blog.arungupta.me/2013/10/java-ee-7-implementations-in-wildfly-tech-tip-3/[Arun Gupta's blog post].
   
  
positive.code: 
  The command returns `{"outcome" => "success"}` in case of success. This command resulted in the following part in the configuration file:
  
      <datasources>
          {...}
          <drivers>
  
negative.code:          ]
  
  The resulting part made by the command in the configuration file are:
  [source,xml]
  ----
      <security-domain name="app" cache-type="default">
        <authentication>
          <login-module code="Database" flag="required">
  