Re: JMS ReplyTo not sent for InOnly Pattern

2010-11-06 Thread igoldsmith
I'm not sure what you mean by creating a sample project. I'm not really a developer. I'm a product manager. I think that the specification of replyTo on an endpoint should always ensure that there is a replyTo specified in messages sent by the JMSProducer, because if the route creator specifies

Re: JMS ReplyTo not sent for InOnly Pattern

2010-11-04 Thread igoldsmith
I've been reading through the source for the JmsProducer class and don't see how this can ever work for InOnly. It seems that the code is looking at the inMessage in the Exchange for a ReplyTo header, and not checking the endpoint definition to see if it's forcing the ReplyTo in the endpoint defi

Re: TransportDisposedIOException

2010-11-04 Thread igoldsmith
Thanks for the quick reply. Yes I'm using AMQ 5.4.1. When you say fixed in trunk, is this the Camel trunk or the AMQ trunk? I'm using AMQ 5.4.1, but with Camel 2.5.0. Ian -- View this message in context: http://camel.465427.n5.nabble.com/TransportDisposedIOException-tp3250474p3250540.html Se

TransportDisposedIOException

2010-11-04 Thread igoldsmith
Using a file connector with the following route definition I get a TransportDisposedIOException whenever I drop a file into the monitored directory. Oddly enough it seems that this doesn't affect the functionality of the system. http://camel.apache.org/schema/web"; xmlns="http://camel.apache.or

JMS ReplyTo not sent for InOnly Pattern

2010-11-04 Thread igoldsmith
I'm trying to setup a fairly simple scenario where I use Camel to pull a document out of a directory on the file system and send it to a JMS queue. I have an application that will read the message from the queue and send a response to the queue specified in the replyTo header of the inbound messa