Hi
What version of Camel are you using? We have fixed some issues in the
http component lately in 1.5.1 and 2.0.
I have just tried you route on Camel 2.0 and I can route the as expected.
Here is some code snippet of the unit test:
public void testJmsHttpJms() throws Exception {
template.sendBody("jms:in", "Hello World");
Endpoint endpoint = context.getEndpoint("jms:out");
endpoint.createConsumer(new Processor() {
public void process(Exchange exchange) throws Exception {
assertEquals("Bye World",
exchange.getIn().getBody(String.class));
}
});
}
@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
public void configure() {
from("jms:in").to("http://localhost/myservice";).to("jms:out");
from("jetty:http://localhost/myservice";).transform().constant("Bye
World");
}
};
}
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Sun, Nov 30, 2008 at 1:10 PM, darren.davison
<[EMAIL PROTECTED]> wrote:
>
> hi, I've been playing with Camel for a couple of days as it looks like it
> will be really useful on an upcoming project for us, but I seem to be
> hitting some basic issues.
>
> One is as follows: trying to take a message off a queue, pass to an http
> endpoint, and place the reply message on another queue. Here's the route;
>
> from("activemq:queue/in")
> .to("http://192.168.1.16:9090/receiver";)
> .to("activemq:queue/reply");
>
> The message is correctly taken from queue/in and used in the call to the
> http listener, but I would have expected the *reply* from the http call
> (body of the response) to end up on the reply queue. What I get on the
> reply queue is a copy of the message from the in queue. Almost as though
> the route had been; from("activemq:queue/in").to("activemq:queue/reply").
> Is this an erroneous assumption?
>
> Cheers,
>
> --
> View this message in context:
> http://www.nabble.com/basic-http-inout-problem-tp20757018s22882p20757018.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
