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
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,
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
