Reports issues with the Spring Websocket XML-based application context:

• Unresolved bean references
• Missing required tags or attributes
• Incorrect property types
• Inconsistent enum properties
• Incorrect types of referenced beans

Example:

  <beans ... >
  
    <bean id="dummyBean" class="java.lang.String"/>
  
    <websocket:message-broker application-destination-prefix="/app"> <!-- Exactly one of <simple-broker> or <stomp-broker-relay> is required -->
        <websocket:stomp-endpoint path="/hello" >
            <websocket:sockjs>
                <websocket:transport-handlers>
                    <ref bean="dummyBean"/> <!-- Bean must be of 'org.springframework.web.socket.sockjs.transport.TransportHandler' type -->
                    <bean class="java.lang.String"/> <!-- java.lang.String' is not assignable to 'org.springframework.web.socket.sockjs.transport.TransportHandler -->
                </websocket:transport-handlers>
            </websocket:sockjs>
        </websocket:stomp-endpoint>
        <websocket:stomp-broker-relay/>
        <websocket:simple-broker prefix="/topic"/>
        <websocket:broker-channel>
            <websocket:executor keep-alive-seconds="10"/>
            <websocket:interceptors>
              <ref bean="dummyBean"/>  <!-- Bean must be of 'org.springframework.messaging.support.ChannelInterceptor' type -->
              <bean class="java.lang.String"/> <!-- java.lang.String' is not assignable to 'org.springframework.messaging.support.ChannelInterceptor' -->
            </websocket:interceptors>
        </websocket:broker-channel>
  </websocket:message-broker>
</beans>