Re: JMS Reply To Issue
Edited as the solution did in fact not work
Hi Andrew,
I looked into the suggestion of removing the property. It appears my initial suggestion for what was wrong was incorrect, it isnt the presence of the header which was driving the creation of the JMSReplyToHandler, this appears to happen as part of the AbstractService as a matter of course.
So as a result of this additional analysis i placed the following into the config i placed above and lo and behold it all worked.
<service name="testService2">
<inbound>
<jms:inbound-endpoint queue="test2.queue" connector-ref="localJmsConnector">
<response-transformers>
<no-action-transformer/>
</response-transformers>
</jms:inbound-endpoint>
</inbound>
<outbound>
<pass-through-router>
<file:outbound-endpoint path="c:/data/out2" connector-ref="fileConnector"/>
</pass-through-router>
</outbound>
</service>
Thank you once again for all your help on this issue. I have been working with Mule for about 2 years now and i still keep on finding new things.
Regards,
Richard
