Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 (Français) » QAnywhere » Connectors » Sending a message from a JMS connector to a QAnywhere client » Addressing JMS messages meant for QAnywhere

 

Mapping JMS messages on to QAnywhere messages

JMS messages are mapped naturally on to QAnywhere messages.

JMS message content

JMS

QAnywhere

Remarks

javax.jms.TextMessage

QATextMessage

Message text copied as Unicode

javax.jms.BytesMessage

QABinaryMessage

Message bytes copied exactly

javax.jms.StreamMessage

N/A

Not supported

javax.jms.MapMessage

N/A

Not supported

javax.jms.ObjectMessage

N/A

Not supported

JMS built-in headers

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.

JMS

QAnywhere

Remarks

JMS Destination

N/A

The JMS destination must be set to the queue specified in the connector property xjms.receiveDestination.

JMS Expiration

Expiration

JMS CorrelationID

InReplyToID

JMS MessageID

N/A

Not mapped.

JMS Priority

Priority

JMS Redelivered

N/A

Not mapped.

JMS ReplyTo and connector's ianywhere.connector.address property value

ReplyToAddress

The connector address is concatenated with the JMS ReplyTo Destination name delimited by '\'.

JMS DeliveryMode

N/A

Not mapped.

JMS Type

QAnywhere message property JMSType

JMS Timestamp

N/A

Not mapped.