anchor.diff:  
   === Transactions
   
  +[[jdbc-server-prepared-statements]]
   === 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
  
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: [source,java]
  ----
  receive(jdbcServer)
          .message(JdbcMessage.execute("SELECT id, title, description FROM todo_entries"));
  send(jdbcServer)
          .messageType(MessageType.XML)<1>
          .message(JdbcMessage.result().dataSet("" +
                  "<dataset>" +
                      "<row>" +
                          "<id>${todoId}</id>"+
                          "<title>${todoName}</title>"+
                          "<description>${todoDescription}</description>" +
                          "<done>false</done>" +
                       "</row>" +
                  "</dataset>"));
  ----
  <1> Tells Citrus that the response has to be interpreted as XML.
  
  