Hi, this worked in that the response mesasge now remains on the output queue. Thanks for that. Unfortunately, the input message is going missing before it reaches the backend service.
Trace logging shows that a 0 byte length request is being sent to the
back-end service which predictably returns an error response. I'm in the
process of setting up a test harness to remove the SSL complexity I have
with the real service, but in principal the 2 line route described in XML
below is causing the servicemix-http component to view the incoming message
as being empty.
What fundamental thing am I not seeing in working with camel-nmr?? Is there
anyone who can tell me why this should fail to transmit an IN message to the
servicemix Exchange?
Cheers,
On Wed, Jun 02, 2010 at 03:58:40AM -0700, iocanel wrote:
> I think that the problem is that your http endpoint is sending the out
> message to the OUT queue and the response never reaches the consumer
> (activemq:IN).
>
> I would try the following:
>
> <camel:route>
> <camel:from uri="activemq:IN?replyTo=OUT"/>
> <camel:inOut uri="nmr:{urn:oms}foo:fooEP"/>
> </camel:route>
--
Darren Davison
Public Key: 0xE855B3EA
signature.asc
Description: Digital signature
