So, base on comments from Scott and Raymond, these are the changes I'm planning
- Fix up the binding.jms XSD to allow "any" content within the <response> . This will allow wireFormat elements from the Tuscany namespace to be included here which can't be done at the moment. Any concerns about this schema modification? - Change the jms binding providers to create a local interface contract by cloning the interface contract from the local reference or service - Change the wire format interface to support a method to reconfigure the binding interface contract. The wire format providers will then have the opportunity to reset the binding interface contract, in either the request or response direction, based on the interface contract style and data format they expect - Change the interface implementation to allow operation input types and output types/faults to be reset independently. - Change the operation model to represent separate input and output wrappers rather than the single wrapper info based model that we have at the moment. This will require a number of changes elsewhere to take account of this Any comments/concerns are most welcome. Regards Simon
