I am thinking that for a jaxws:client, the easiest will be to define a integration gateway which uses the same interface as the client. On the other end of the channel can be a service activator that executes the actual jaxws:client.
For a jaxws:endpoint, instead of using the actual impl, I also define a integration gateway for the interface which also ends in a service activator which executes the original impl. The jaxws:endpoint will reference the gateway instead of the impl. Now I think I only have to worry about message serialisation when using a message-store. Will see how I go. On Fri, Apr 12, 2013 at 10:27 AM, Jason Pell <ja...@pellcorp.com> wrote: > Topics of interest. > > > http://cxf.547215.n5.nabble.com/re-CXF-with-Sprint-Integration-td5501007.html > > http://cxf.547215.n5.nabble.com/CXF-embedded-within-a-SpringIntegration-Context-td5158465.html > > > On Wed, Apr 10, 2013 at 8:25 PM, Jason Pell <ja...@pellcorp.com> wrote: > >> Is there any plans to add namespace support for jaxws endpoint and client >> to spring integration? >> >> I am envisioning ability to define jaxws:client as a gateway with a queue >> channel in between to provide decoupling of client from transport >> >> And endpoint as a end of a channel - service activator maybe. >> >> There is camel support for cxf not sure how that works >> >> I am looking at using spring integration for async support rather than jms >> > >
