Yes, I also realised my approach will not work for multiple methods as the service-activator expects a method name. Back to doing more reading in the spring integration docs and samples.
On Fri, Apr 12, 2013 at 1:06 PM, Willem jiang <[email protected]>wrote: > Yeah, you are not the first one who has this idea. > I think the easiest way is implement a transport of sprint integration, > you can setup the {Input|Output} channel for the conduit or destination. > The difficult part could how to implement the CXF Continuation API with > spring integration async support. > > BTW, CXF supports the Servlet3 async invocation API out of box. > > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > > > On Friday, April 12, 2013 at 8:27 AM, Jason Pell 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 <[email protected] (mailto: > [email protected])> 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 > > >
