anchor.diff:  });
   -------------------------------------------------------------------------------------------------------
   
  -If you make calls to {javadocBase}fi/evident/dalesbred/Database.html[Database] without and explicit transaction, by default
  -a new transaction is started for each call, but you can disallow this, in
  -which case exceptions are thrown for calls without an active transaction:
  -
  -[source,java]
  -db.setAllowImplicitTransactions(false);
  -
  -Nested transactions are supported if your database supports them:
  -
  -[source,java]
  -db.withTransaction(Propagation.NESTED, new TransactionCallback<Result>() { ... });
  -
   Annotation based transactions
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
  -The above transaction mechanism is a decent building block for implementing higher
  -level abstractions, but it's quite verbose to use in Java. Therefore Dalesbred provides
  +If you are not using Java 8, the anonymous inner classes required by transaction callbacks
  +are quite verbose. Therefore Dalesbred provides
   a simple support for building transactional proxies for services:
   
   [source,java]
  
positive.code: Add the following to your project:
  
  [source,groovy]
  dependencies {
      compile 'fi.evident.dalesbred:dalesbred:0.6.0'
  }
  
  For the JUnit test-support classes, add the following:
  
  
negative.code: service.frobnicate(); // this call will have a transaction wrapped around it
  -------------------------------------------------------------------------------------------------------
  
  External transaction manager
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  If you are using http://projects.spring.io/spring-framework/[Spring Framework] or
  https://code.google.com/p/google-guice/[Guice], Dalesbred can integrated with them for transaction
  management. Consult the <<_integrations,Integrations>>-section for details.
  
  Implicit transactions
  ~~~~~~~~~~~~~~~~~~~~~
  
  If you make calls to {javadocBase}fi/evident/dalesbred/Database.html[Database] without and explicit transaction, by default
  a new transaction is started for each call, but you can disallow this, in
  which case exceptions are thrown for calls without an active transaction:
  
  [source,java]
  db.setAllowImplicitTransactions(false);
  
  Nested transactions
  ~~~~~~~~~~~~~~~~~~~
  
  Nested transactions are supported if your database supports them:
  
  [source,java]
  -------------------------------------------------------------------------------------------------------
  db.withTransaction(Propagation.NESTED, new TransactionCallback<Result>() {
      ...
  });
  -------------------------------------------------------------------------------------------------------
  
  Miscellaneous features
  ----------------------
  
  