anchor.diff:  WebSocket client. You can configure the STOMP credentials that are used for all TCP
   connections created on behalf of clients. This is exposed in both the XML namespace
   and Java configuration as the `clientLogin` and `clientPasscode` properties with default
  -values of `guest`and `guest`.
  +values of `guest` and `guest`.
   
   NOTE: The STOMP broker relay always sets the `login` and `passcode` headers on every `CONNECT`
   frame that it forwards to the broker on behalf of clients. Therefore, WebSocket clients
  
positive.code: mobile applications where it is common to use headers for authentication).
  
  The https://tools.ietf.org/html/rfc6455#section-10.5[WebSocket protocol, RFC 6455]
  "`doesn't prescribe any particular way that servers can authenticate clients during
  the WebSocket handshake.`" In practice, however, browser clients can use only standard
  authentication headers (that is, basic HTTP authentication) or cookies and cannot (for example)
  provide custom headers. Likewise, the SockJS JavaScript client does not provide
  a way to send HTTP headers with SockJS transport requests. See
  
negative.code: 
  You can send a message to user destinations from any application
  component by, for example, injecting the `SimpMessagingTemplate` created by the Java configuration or
  the XML namespace. (The bean name is `brokerMessagingTemplate` if required
  for qualification with `@Qualifier`.) The following example shows how to do so:
  
  [source,java,indent=0]
  