title: Why does STOMP functionality in spring-websocket depend on Spring MVC?
body: <p>Currently, I am trying to use STOMP with websockets using webflux. In order to send a message to a STOMP topic, I need to use <code>SimpMessagingTemplate</code>, which is contributed by spring boot auto configuration when I add <code>@EnableWebSocketMessageBroker</code></p>
  
  <p>But the problem with this is, <code>@EnableWebSocketMessageBroker</code> indirectly expects me to have <code>spring-mvc</code> library in classpath</p>
  
  <p><code>@EnableWebSocketMessageBroker</code> <code>@Import</code>s <code>DelegatingWebSocketMessageBrokerConfiguration</code> which extends <code>WebSocketMessageBrokerConfigurationSupport</code> &amp; <code>WebSocketMessageBrokerConfigurationSupport#stompWebSocketHandlerMapping</code> method expects the class <code>HandlerMapping</code> to be returned</p>
  
  <p>My question is</p>
  
  <ol>
  <li>How to integrate STOMP with webflux without webmvc</li>
  <li>Why is the autoconfiguration forcing us to have mvc in classpath (and potentially conflict with webflux)</li>
  </ol>