Hi all,
When using JMS for request/reply messaging, you usually use one of two
patterns: the JMS Message ID pattern or the Correlation ID pattern. With the
JMS Message ID pattern, the service (in this case XFire) would populate the
reply message's correlation ID with the message ID of the request message.
With the Correlation ID pattern, the client needs to generate a unique ID and
set that as the correlation ID of the request message and the service would
populate the reply message correlation ID with the correlation ID of the
request message.
XFire only supports the Correlation ID pattern (in the JMSChannel class). Has
there been any discussion on supporting both patterns? Perhaps there can be a
configuration setting when the jmsTransport bean? Or the code could use the
correlation ID from the request message if it is available or else use the
message ID? When using WebSphere MQ the message ID generated is guaranteed to
be unique so the JMS Message ID pattern is preferable.
Thank you,
Josh
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
