anchor.diff:  
   Just use this before-test bean in the Spring bean application context and the purge endpoint action is active. Obsolete messages that are waiting on the message endpoints for consumption are purged before the next test in line is executed.
   
  -TIP: Purging message endpoints becomes also very interesting when working with server instances in Citrus. Each server component automatically has an inbound message endpoint where incoming messages are stored to internally. Citrus will automatically use this incoming message endpoint as target for the purge action so you can just use the server instance as you know it from your configuration in any purge action.+TIP: Purging message endpoints becomes also very interesting when working with server instances in Citrus. Each server component automatically has an inbound message endpoint where incoming messages are stored to internally. Citrus will automatically use this incoming message endpoint as target for the purge action so you can just use the server instance as you know it from your configuration in any purge action.
  
positive.code: .Java DSL runner
  [source,java]
  ----
  @Autowired
  @CitrusTest
  public void purgeTest() {
      purgeEndpoints(action ->
  
negative.code: .Java DSL designer
  [source,java]
  ----
  @CitrusTest
  public void purgeTest() {
      purgeEndpoints()
  