activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Vincent <Stephen.Vinc...@sas.com>
Subject RE: No correlation ID in HTTP header when using RESTful interface
Date Wed, 12 Sep 2012 04:36:29 GMT
	I am using version 5.6.0.  Here is an excerpt from the debug messages my HTTP client code
reports regarding the GET request:

DEBUG >>> GET /demo/message/myqueue?type=queue&consumer.prefetchSize=1&clientId=0F371438-8939-4D0D-A
279-35CB9EE77FE0&readTimeout=1000 HTTP/1.1
DEBUG >>> Host: d22275:8161
DEBUG >>> Accept: */*
DEBUG >>> Accept-Charset: iso-8859-1,*,utf-8
DEBUG >>> Accept-Encoding: identity
DEBUG >>> Accept-Language: en
DEBUG >>> User-Agent: SAS/9
DEBUG >>>
DEBUG <<< HTTP/1.1 200 OK
DEBUG <<< Set-Cookie: JSESSIONID=ircbgnvtz49413se5gy16uppm;Path=/demo
DEBUG <<< Expires: Thu, 01 Jan 1970 00:00:00 GMT
DEBUG <<< Content-Type: text/xml;charset=UTF-8
DEBUG <<< destination: queue://myqueue
DEBUG <<< id: ID:d22275-1706-1347423130989-3:1:1:1:1
DEBUG <<< Content-Length: 38
DEBUG <<< Server: Jetty(7.6.1.v20120215)
DEBUG <<<

	When using the RESTful HTTP interface, the only way I have found to set the correlation ID
on a per message basis, is to use a content-type of "application/x-www-form-urlencoded" and
add a "&JMSCorrelationID=<mycorrelid>" parameters along with my "&body=<mymsg>"
parameter.  Is there a way to set the correlation IDs(per message) when using a content-type
of "text/xml"?

Thanks,
sv
sasasasasasasasasasasasasasasasasasasasasasasasasasasasasasasasas
Stephen Vincent
Platform R&D
Tel: + 1 919 531 7556
stephen.vincent@sas.com



Mime
View raw message