anchor.diff:  <3> Verify that the prepared statement has been closed.
   
   As you might have noticed, callable statements and prepared statements have nearly the same workflow in Citrus. The only
  -difference in the creation of the statement itself.
  +difference in the creation of the statement itself. It is also the case that the verification of
  +`createCallableStatement` and `closeStatement` messages has to be activated via configuration. For more information,
  +please have a look at the <<jdbc-server-configuration>> section.
   
   [[jdbc-server-configuration]]
   === Configuration
  
positive.code: 
  === Transactions
  
  === Prepared statements
  Because prepared statements work slightly different than simple database queries, the validation of those is also
  slightly different. Currently, Citrus offers you the possibility to verify that your application has created the
  
negative.code: | States that the connection has been closed. The evaluation of connections has to be enabled
  via the endpoint configuration.
  
  | `JdbcMessage.createStatement()`
  | receive
  | States that a statement has been created. The evaluation of statement handling has to be enabled via the endpoint
  configuration.
  
  | `JdbcMessage.createPreparedStatement(String sql)`
  | receive
  | States that a SQL statement matching the given expression has been created. The evaluation of statement handling
  has to be enabled via the endpoint configuration.
  
  | `JdbcMessage.createCallableStatement(String sql)`
  | receive
  | States that a callable statement referencing a function or procedure that is matching the given expression has been
  created. The evaluation of statement handling has to be enabled via the endpoint configuration.
  
  | `JdbcMessage.closeStatement()`
  | receive
  