Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 27 Sep 2012 03:51:07 +1100 (NCT)
From: "Stephen Vincent (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <830411276.129135.1348678267845.JavaMail.jiratomcat@arcas>
In-Reply-To: <23363571.116873.1348497727885.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4072) RESTful HTTP interface responses do
 not contain a correlation ID header
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMQ-4072?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D134639=
48#comment-13463948 ]=20

Stephen Vincent commented on AMQ-4072:
--------------------------------------

   I would like that, but finding the time will be difficult.  I am current=
ly under the gun with respect to some deadlines, so can't be anytime soon. =
=20

   With respect to the needs of my client app, I should mention it is a C-b=
ased client.  In the past, I already developed C-based interfaces that hop =
over through JNI to a JVM where I load a JMS provider.  However, now I am d=
eveloping C-based interfaces that avoid a client-side JVM.  If I understand=
 things, my two top choices are to access the ActiveMQ broker RESTfully ove=
r HTTP, or develop a C-wrapper to the ActiveMQ-CPP client library.  The lat=
ter seems involved and includes dependencies on open source client librarie=
s such as ActiveMQ-CPP and the APR.  Given that someone else in my organiza=
tion has already developed some C-based HTTP interfaces, I thought it would=
 be best to choose the former, and make use of the HTTP protocol.

   The C-based HTTP client code I call, establishes a connection using a UR=
L.  Once connected, I can make many POST and GET requests, but I am encount=
ering problems with respect to correlation ID's.  I cannot change the URL u=
nless I re-connect, and I don't want to do that.  So, the only way I have f=
ound to POST messages within the same session/connection and with varying c=
orrelation ID's, is to use a content-type of "application/x-www-form-urlenc=
oded".  That is a bit restrictive because then my users have to make sure t=
he data is formatted correctly.  For example, you can't just send any text,=
 without having to worry about special characters such as ampersand("&").  =
Also, the only way I have found to obtain the correlation ID when GETting a=
 message, is when the correlation ID was actually put in the message as a s=
tring property, and I must know the name of the property.  Making use of th=
e JMSCorrelationID header field would be ideal, but the current MessageServ=
let doesn't support it with respect to the pattern I mention above.

Thanks,
sv
               =20
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>
>                 Key: AMQ-4072
>                 URL: https://issues.apache.org/jira/browse/AMQ-4072
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0
>         Environment: RESTful HTTP client
>            Reporter: Stephen Vincent
>             Fix For: 5.8.0
>
>         Attachments: CorrelId.java
>
>
> When using a RESTful HTTP client to GET a message that has a correlation =
ID, the correlation ID is not sent as a header in the response from the bro=
ker.  This inhibits my RESTful HTTP client from performing request-response=
.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira