Fuse ESB Enterprise - Migration Guide - Transport Protocol Changes

Transport Protocol Changes

HTTPS transport

The HTTPS transport can now have its security properties configured by the sslContext element in the Apache ActiveMQ configuration.

Stomp 1.1

The following changes have been made to the implementation of the Stomp 1.1 protocol:

Since Apache ActiveMQ 5.7.0, in the case where a particular header property is defined multiple times in a Stomp message, the first header value is now taken to be the actual value of the header. In earlier Apache ActiveMQ versions, the last header value is used (which does not conform with the Stomp 1.1 specification).
Since Apache ActiveMQ 5.6.0, the spaces around header keys and values are no longer trimmed automatically (this is in order to be consistent with the Stomp 1.1 specification). This could affect the processing of headers in your Stomp clients, when migrating to Apache ActiveMQ 5.7.0.

WebSocket transport

For the WebSocket transport, it is now possible to initialize any of the parameters on the underlying the Jetty servlet holder instance by using the websocket. prefix on the transport server URI. This works on either the ws: or the wss: URIs.

Comments powered by Disqus