anchor.diff:  ----
   
   When the user runs the Stateful Session Bean he can implement
  -interface https://javaee.github.io/javaee-spec/javadocs/javax/ejb/SessionSynchronization.html[javax.ejb.SessionSynchronization]
  +interface https://jakarta.ee/specifications/enterprise-beans/4.0/apidocs/jakarta/ejb/sessionsynchronization[jakarta.ejb.SessionSynchronization]
   (or to use annotations) for the definition of the synchronization callbacks onto the bean.
   The session synchronization defines three methods.
   Of these three methods `afterBegin` is not connected to the transaction synchronization so we will not discuss it further.
  
positive.code:    shows only one resource to be part of the two-phase commit handling.
     That's intentional for the log not being too long.
  * the `section-1` refers to the point where the transaction is started. The
    https://javaee.github.io/javaee-spec/javadocs/javax/transaction/Synchronization.html[JTA synchronizations]
    are registered and the transaction is added to be handled by transaction reaper
    (the transaction reaper is an independent thread taking care of transaction timeouts,
      see more at http://narayana.io/docs/project/index.html#d0e2032[section Transaction timeouts]
  
negative.code: 
  JTA API gives a chance to react to the event of a finishing transaction.
  The definition says that transaction manager announces the even of `beforeCompletion` and `afterCompletion`
  which are defined by the interface https://jakarta.ee/specifications/transactions/2.0/apidocs/jakarta/transaction/synchronization[jakarta.transaction.Synchronization].
  The https://jakarta.ee/specifications/transactions/2.0/apidocs/jakarta/transaction/synchronization#beforeCompletion--[`beforeCompletion`]
  callback is invoked at time the transaction manager starts to commit the global transaction. The invocation is processed in the transaction context.
  The https://jakarta.ee/specifications/transactions/2.0/apidocs/jakarta/transaction/synchronization#afterCompletion-int-[`afterCompletion`]
  is invoked after the transaction is committed or rolled-back (and is processed outside of the transaction context).
  
  The user needs just to create a simple Java POJO and implement the interface.
  