How Stomp Messages are Sent and Consumed from JMS or Core

WARNING - TOPIC NOT WRITTEN - TOPIC ID: 868

This topic has not yet been written. The content below is from the topic description.
45.1.3.2. Send and consuming Stomp message from JMS or HornetQ Core API Stomp is mainly a text-orientated protocol. To make it simpler to interoperate with JMS and HornetQ Core API, our Stomp implementation checks for presence of the content-length header to decide how to map a Stomp message to a JMS Message or a Core message. If the Stomp message does not have a content-length header, it will be mapped to a JMS TextMessage or a Core message with a single nullable SimpleString in the body buffer. Alternatively, if the Stomp message has a content-length header, it will be mapped to a JMS BytesMessage or a Core message with a byte[] in the body buffer. The same logic applies when mapping a JMS message or a Core message to Stomp. A Stomp client can check the presence of the content-length header to determine the type of the message body (String or bytes).