Also, By the way can you think of a temporary workaround offhand? The end point I'm communicating with is not something built with SCA. It is an legacy request/response messaging pattern exposed via WebsphereMQ.
So it just expects a JMS message with a text payload. The payload is an XML document (proprietary schema). -----Original Message----- From: Hatfield, Dan Sent: Friday, January 08, 2010 11:11 AM To: '[email protected]' Subject: RE: Re: Thanks Simon. It is raised - https://issues.apache.org/jira/browse/TUSCANY-3418 -----Original Message----- From: Simon Laws [mailto:[email protected]] Sent: Friday, January 08, 2010 10:55 AM To: [email protected] Subject: Re: Hi Dan Yes, I'm seeing it here also. In this case the WireFormatJMSTextReferenceInterceptor is being added to the wire twice for some reason and that's causing the problem. Don't know why yet but can you raise a JIRA [1] for the problem and I'll look at making a fix for it. Thanks Simon [1] https://issues.apache.org/jira/browse/TUSCANY
