I checked in an initial pass at a test to motivate this work. You can find it here [1] but of course it doesn't do anything useful yet as the code doesn't actually work. The composite for this test shows wireFormat.jmsTextXML being used on request messages and wireFormat.jmsObject being used on response messages.
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0" targetNamespace="http://helloworld" xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0" xmlns:hw="http://helloworld" name="helloworld"> <component name="HelloWorldReferenceComponent"> <implementation.java class="org.apache.tuscany.sca.binding.jms.format.jmstextxmlinjmsobjectout.helloworld.HelloWorldReferenceImpl" /> <reference name="helloWorldService1" > <binding.jms> <destination name="HelloWorldService1"/> <response> <tuscany:wireFormat.jmsObject/> </response> <tuscany:wireFormat.jmsTextXML/> </binding.jms> </reference> </component> <component name="HelloWorldServiceComponent1"> <implementation.java class="org.apache.tuscany.sca.binding.jms.format.jmstextxmlinjmsobjectout.helloworld.HelloWorldServiceImpl" /> <service name="HelloWorldService"> <binding.jms> <destination name="HelloWorldService1"/> <response> <tuscany:wireFormat.jmsObject/> </response> <tuscany:wireFormat.jmsTextXML/> </binding.jms> </service> </component> </composite> With binding.jms this could be useful as the response destination may be completely divorced from the source of the request message and therefore have different requirements. Regards Simon [1] http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/itest/jms-format/src/test/java/org/apache/tuscany/sca/binding/jms/format/FormatJMSTextXMLInJMSObjectOutTestCase.java
