-
1. Re: Need clarification on destination for JMSRouter Quicksta
scottdawson May 12, 2009 10:00 AM (in response to ezanih)Look at the "runtest" target in build.xml and you'll see values you can use for the 2 arguments. In fact, "ant runtest" will do it for you. According to build.xml, the value for the second argument should be queue/quickstart_jms_router_routeTo.
Regards,
Scott -
2. Re: Need clarification on destination for JMSRouter Quicksta
ezanih May 12, 2009 11:37 PM (in response to ezanih)Ok, I got it to work. Just a short question: why do we need a Correlation ID ? We already have a Message ID which uniquely identifies the message so why do we need a Correlation ID ? What is a Correlation ID and what is a Message ID ? What is the difference between the two ?
Many thks! -
3. Re: Need clarification on destination for JMSRouter Quicksta
ezanih May 13, 2009 4:13 AM (in response to ezanih)Ok, I answered my own question which could easily be gotten from the Internet, which I'll share with you all.
Basically a Correlation ID allows a requestor who has sent several requests each of which requires responses, to match which response to which request.
As we all know, each message (whether request or response) has a MessageID. When responding to a request, just set the Correlation ID of the response to the original request's MessageID, and hey presto! you have a way to match a response to the original request!