anchor.diff:  ====
   
   A sequence node is labeled with the constant +SEQUENCE+ and with the generator key of the sequence.
  -A unique constraint is applied on the property +sequence_name+ to avoid the same sequence name is used twice in node having the same generator key.
  +A unique constraint is applied on the property +sequence_name+ to avoid the same sequence name is used twice in nodes having the same generator key.
   The property +current_value+ stores the next value of the sequence.
   
   Note that when a different strategy is selected for an entity, we won't throw an exception but we will fall-back to this representation. The only difference is that we will apply
  
positive.code:     <version>{hibernate-ogm-version}</version>
  </dependency>
  ----
  Alternatively you can find the required libraries in the distribution package on https://downloads.sourceforge.net/project/hibernate/hibernate-ogm/{hibernate-ogm-version}/hibernate-ogm-modules-{hibernate-ogm-version}-jbossas-72-dist.zip[SourceForge]
  
  .2. Add the following properties:
  
  
negative.code: 
  Neo4j operations can be executed only inside a transaction.
  Unless a different +org.hibernate.engine.transaction.jta.platform.spi.JtaPlatform+ is specified, OGM will use a default one to integrate with the Neo4j transaction mechanism.
  This means that you can start and commit transaction using the Hibernate session.
  
  The drawback is that it is not possible at the moment to let Neo4j participate in managed JTA transactions spanning several resources (see issue https://hibernate.atlassian.net/browse/OGM-370[OGM-370]).
  
  .Example of starting and committing transactions
  ====
  