Hi Good question. Looks like there is something called DestinationResolver org.springframework.jms.support.destination.DestinationResolver
Could you check upon this if that could be used? Maybe it could be used to lookup the MQDestQueue bean id in the application context, to be used as Destination. I am wondering if you can inject your own DestinationResolver to the camel jms endpoint. If it's the way to get we improve camel to expose a setter so you can inject your own resolver. Please research a bit, and write back. Then we can create a ticket in JIRA so we can get a nice solution in Camel to work with MQ queues. /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Thu, Dec 4, 2008 at 3:23 PM, Stephen J <[EMAIL PROTECTED]> wrote: > > Does anyone know how to set the targetClient property to a Websphere MQ > destination? Right now Camel is putting messages on my MQ queue in a JMS > format. This causes extra headers to be appended to the message body, so > when you pull messages off the MQ queue with a regular MQ client all those > extra headers show up in the message body. > > The way to fix this is to specify targetClient=1 on the MQ queue you are > sending to, but I can't figure out how to tell Camel to do that. > > If I could configure the MQ destination something like this: > <bean id="MQDestQueue" class="com.ibm.mq.jms.MQQueue"> > <constructor-arg index="0" value="AMQ.TEST.Q"/> > <property name="targetClient" value="1" /> > </bean> > > Then have camel route to that queue, I think that would solve the problem. > I can't figure out how to specify queue destinations like the above example. > Does anyone know how to do this, or how to fix this issue with sending to a > Websphere MQ queue? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Camel-to-Websphere-MQ-communication-tp20834360s22882p20834360.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
