There is currently no way for a client application to set the accepted STOMP version value. In the org.springframework.messaging.simp.stomp.DefaultStompSession.afterConnected() method, the code calls
This overrides any version that the application may have requested in the StompHeaders. The preferred behavior would be to check the StompHeaders for an "accept-version" header and if found use that value instead of the hard-coded "1.1,1.2" value.
The specific use case I have for this feature is that there is currently a bug in the Apache Artemis message broker that affects STOMP 1.2 but not STOMP 1.1. Therefore to avoid this bug I would like to specify STOMP 1.1 but using a Spring based client I am unable to do so.