...
Additionally some data elements may be repeated in message header/property fields for convenience and queue operation, such as the use of selectors. Data which might be considered confidential should not appear in message headers.
Currently the following message elements are proposed to be transmitted in the header as well as in the message xml:
Protocol/XML field | JMS header/property | NMS header/property |
|---|---|---|
correlationID | JMSCorrelationID | NMSCorrelationID |
replyTo To | JMSDestination | NMSReplyTo NMSDestination |
ReplyTo | JMSReplyTo |
|
MessageType |
|
|
BitRepositoryCollectionID | NMSReplyTo | |
(root element - message type) | org.bitrepository.messages.collectionid type | org.bitrepository.messages.collectionid |
- correlationID (present by default)
- replyTo (present by default)
- BitRepostitoryCollectionID - enables pillars to quickly discard irrelevant messages on a common topic
- MessageType
- To (destination topic/queue)
...
type | |
BitRepositoryCollectionID | org.bitrepository.messages. |
...
collectionid | org.bitrepository.messages.collectionid |
...
| Child pages (Children Display) | ||||||||
|---|---|---|---|---|---|---|---|---|
|