On Jan 24, 2008 8:42 AM, DominicTulley <[EMAIL PROTECTED]> wrote:
>
> Thanks for the explanation Roman, I think it makes more sense to me now.
> It sounds like camel's automatic handling of replyto becomes more useful if
> we are bridging between brokers - then the server may not be able to access
It also makes loads of sense when talking to other InOut protocols
like http. For example
from("jms:queue:test").to("http://localhost/test";)
It will take care sending the http response to the reply to queue.
> the destination set in the ReplyTo from the original sender, so the replies
> go in steps, retracing the route the original message took.
>
> On the exception front, it also sounds better. It wasn't clear to me if the
> exception was in response to my message, my reply, or some expectation
> within the system. It sounds like it was a system expectation which I
> wasn't honouring so that's great too since the expectation doesn't exist for
> me now :-)
>
> I'm off to find my next hurdle now!
>
> -Dominic
>
> --
> View this message in context:
> http://www.nabble.com/TimeoutException-when-using-ReplyTo--tp15043879s22882p15064145.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://open.iona.com
