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: | States that the connection has been closed. The evaluation of connections 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.createStatement()`
  | receive
  | States that a statement has been created. The evaluation of statement handling has to be enabled via the endpoint
  configuration.
  
  | `JdbcMessage.closeStatement()`
  | receive
  
negative.code: <2> Verify that the statement has been executed with the parameters `1,sample,A sample todo,false`.
  <3> Verify that the prepared statement has been closed.
  
  Please notice, that the verification of `createPreparedStatement` and `closeStatement` messages has to be activated
  via configuration. For more information, please have a look at the <<jdbc-server-configuration>> section.
  
  [[jdbc-server-callable-statements]]
  === Callable statements / stored procedures
  As well as prepared statements, callable statements are different from simple queries. Callable statements are used
  on jdbc level to access stored procedures, functions, etc. on the database server.
  