When created from STOMP frame content, the actual STOMP headers are stored in the native header sub-map managed by the parent class {@link org.springframework.messaging.support.NativeMessageHeaderAccessor}while the parent class {@link org.springframework.messaging.simp.SimpMessageHeaderAccessor} managescommon processing headers some of which are based on STOMP headers (e.g. destination, content-type, etc).
An instance of this class can also be created by wrapping an existing {@code Message}. That message may have been created with the more generic {@link org.springframework.messaging.simp.SimpMessageHeaderAccessor} inwhich case STOMP headers are created from common processing headers. In this case it is also necessary to invoke either {@link #updateStompCommandAsClientMessage()} or{@link #updateStompCommandAsServerMessage()} if sending a message anddepending on whether a message is sent to a client or the message broker. @author Rossen Stoyanchev @since 4.0
|
|
|
|