QAnywhere messages are mapped naturally on to JMS messages.
QAnywhere | JMS | Remarks |
---|---|---|
QATextMessage |
javax.jms.TextMessage |
message text copied as Unicode |
QABinaryMessage |
javax.jms.BytesMessage |
message bytes copied exactly |
The following table describes the mapping of built-in headers. In C++ and JMS, these are method names; for example, Address is called getAddress() or setAddress() for QAnywhere, and getJMSDestination() or setJMSDestination() for JMS. In .NET, these are properties with the exact name given below; for example, Address is Address.
QAnywhere | JMS | Remarks |
---|---|---|
Address |
JMSDestination and JMS property ias_ToAddress |
If the destination contains a backslash, you must escape it with a second backslash. Only the JMS part of the address is mapped to the Destination. Under rare circumstances, there may be an additional QAnywhere address suffix if a message loops back into QAnywhere. This is put in ias_ToAddress. |
Expiration |
JMSExpiration |
|
InReplyToID |
N/A |
Not mapped. |
MessageID |
N/A |
Not mapped. |
Priority |
JMSPriority |
|
Redelivered |
N/A |
Not mapped. |
ReplyToAddress |
JMS property ias_ReplyToAddress |
Mapped to JMS property. |
Connector's xjms.receiveDestination property value |
JMSReplyTo |
ReplyTo set to Destination used by connector to receive JMS messages. |
Timestamp |
N/A |
Not mapped. |
N/A | JMSTimestamp | When mapping a JMS message to a QAnywhere message, the JMSTimestamp property of the QAnywhere message is set to the JMSTimestamp of the JMS message. |
Timestamp | N/A | When mapping a QAnywhere message to a JMS message, the JMSTimestamp of the JMS message is set to the time of creation of the JMS message. |
QAnywhere properties
Addressing JMS messages meant for QAnywhere
Discuss this page in DocCommentXchange.
|
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0 |