anchor.diff:  		}
   	}
   ----
  +
  +Applications may also implement `ExecutorChannelInterceptor` which is a sub-interface
  +of `ChannelInterceptor` with callbacks in the thread in which the messages are handled.
  +While a `ChannelInterceptor` is invoked once for per message sent to a channel, the
  +`ExecutorChannelInterceptor` provides hooks in the thread of each `MessageHandler`
  +subscribed to messages from the channel.
   
   Note that just like with the `SesionDisconnectEvent` above, a DISCONNECT message
   may have been sent from the client, or it may also be automatically generated when
  
positive.code: [source,java,indent=0]
  [subs="verbatim,quotes"]
  ----
  	public class MyChannelInterceptor extends ChannelInterceptorAdapter {
  
  		@Override
  		public Message<?> preSend(Message<?> message, MessageChannel channel) {
  
negative.code: 
  
  
  [[websocket-stomp-appplication-context-events]]
  === Events
  
  Several `ApplicationContext` events (listed below) are published and can be
  received by implementing Spring's `ApplicationListener` interface.
  