anchor.diff:  		}
   	}
   ----
  +
  +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
  +the WebSocket session is closed. In some cases an interceptor may intercept this
  +message more than once per session. Components should be idempotent with regard to
  +multiple disconnect events.
   
   
   
  
positive.code: 	}
  ----
  
  A custom `ChannelInterceptor` can extend the empty method base class
  `ChannelInterceptorAdapter` and use `StompHeaderAccessor` or `SimpMessageHeaderAccessor`
  to access information about the message.
  
  [source,java,indent=0]
  
negative.code: implement their own reconnect logic.
  ====
  
  The above events reflect points in the lifecycle of a STOMP connection. They're not meant
  to provide notification for every message sent from the client. Instead an application
  can register a `ChannelInterceptor` to intercept every incoming and outgoing STOMP message.
  For example to intercept inbound messages:
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  