Wayne Keenan wrote:
On Mon, Jan 25, 2010 at 4:25 AM, Willem Jiang wrote:
Hi Wayne,
I'm not sure we need to populate the headers for the HTTP PUT method.
Can you point me out if there any specification for it ?
Willem
I looked at the RFC's for http 1.0 and 1.1, to me it doesn't appear to
p
On Mon, Jan 25, 2010 at 4:25 AM, Willem Jiang wrote:
> Hi Wayne,
>
> I'm not sure we need to populate the headers for the HTTP PUT method.
> Can you point me out if there any specification for it ?
>
> Willem
>
>
> I looked at the RFC's for http 1.0 and 1.1, to me it doesn't appear to
preclude us
Hi Wayne,
I'm not sure we need to populate the headers for the HTTP PUT method.
Can you point me out if there any specification for it ?
Willem
Wayne Keenan wrote:
Hi Willem,
Thanks very much, I can confirm that with 2.2-SNAPSHOT I can obtain the URI
QUERY parameters from the camel header(s)
Hi Willem,
Thanks very much, I can confirm that with 2.2-SNAPSHOT I can obtain the URI
QUERY parameters from the camel header(s) when POSTing content-type of
application/octet-stream.
I did notice that a HTTP PUT doesn't populate the headers with the URI Query
parameter
Regards
Wayne
On Fri, Ja
Hi Wayne,
I commit a patch of CAMEL-2386, please check out the last
camel-2.2-SNAPSHOT to verify it :)
Willem
Willem Jiang wrote:
I just did a quick test on camel trunk, you can get the URL parameters
by using the
exchange.getIn().getHeader(Exchange.HTTP_QUERY)
When you post the binary data
I just did a quick test on camel trunk, you can get the URL parameters
by using the
exchange.getIn().getHeader(Exchange.HTTP_QUERY)
When you post the binary data with URI Query.
I just took a look at camel-http and found we could parser the URL
parameter for the post method.
So I created a JI
Hi,
Nope, I am POSTing binary data as the body with a content-type of '
application/octet-stream', and am sending additional parameters in the URI
Query that are not appearing as Camel headers.
Perhaps this is not 'best practice', and the body should be multipart MIME
encoded so it can be POST'e
On Wed, Jan 20, 2010 at 10:40 AM, Wayne Keenan wrote:
> Hi,
>
> Apologies, I didn't word my previous email very well; what I should have
> also mentioned for clarity is that if I do this:
>
>
> http://0.0.0.0:8080/endpoint"/>
>
>
> ${id}
>
Hi
Please always write which version of Camel you are using.
And others listening in, do that as well. Its important for us to know!
On Wed, Jan 20, 2010 at 10:02 AM, Wayne Keenan wrote:
> Hi,
>
> I have a Jetty endpoint that when recieving a message will perform the
> processing asynchronously
Willem Jiang wrote:
Wayne Keenan wrote:
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang
wrote:
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
http://0.0.0.0:80
Hi,
Is your post request using "application/x-www-form-urlencoded" as the
content-type ?
If so , you should get the parameters from the message header.
Willem
Wayne Keenan wrote:
Hi,
I believe I have found the trouble I am having. I think this bug still
exists in the 2.1.0 release:
http://
Wayne Keenan wrote:
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang wrote:
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
http://0.0.0.0:8080/endpoint"/>
Hi,
I believe I have found the trouble I am having. I think this bug still
exists in the 2.1.0 release:
http://issues.apache.org/activemq/browse/CAMEL-1806
The docs says from: http://camel.apache.org/jetty.html says:
*Camel also populates all request.parameter and request.headers. For
example,
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang wrote:
> Hi,
>
> Can you try to set the ID into the message header instead of the message
> body ? In this way you can the Request object back :)
>
>
> >>
> >> http://0.0.0.0:8080/endpoint"/>
> >>
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
>>
>> http://0.0.0.0:8080/endpoint"/>
>>
>>
>> ${id}
>>
>>
>>
>>
>>
Hi,
Apologies, I didn't word my previous email very well; what I should have
also mentioned for clarity is that if I do this:
http://0.0.0.0:8080/endpoint"/>
${id}
The same bean is able to obtain the HTTPServlet
Hi,
I have a Jetty endpoint that when recieving a message will perform the
processing asynchronously and syncronously return a correlationId so the
client can come back later to another endpoint to see how processsing is
going.
I found an example on the mailing list of how to pass the HttpSession
17 matches
Mail list logo
