Yes, no prob. I'll just have to find a nice tool to edit the wsdl. Or just do another java-first project in order to generate a wsdl from code, then import it the asynchronous app ;-) I hope the asynchronous WS server will be soon normalized the same way as the jax-rs asynchronous server (quite easy to use)
Yes, i'm lazy. Another question : does CXF's @WebServiceProvider supports the asynchronous invoke ? 2012/11/12 Freeman Fang <[email protected]> > Hi, > > Actually it's no such limitation that you must use wsdl first way with > async, you can write class like GreetMeSometimeResponse yourself, though > it's a little bit hard and error prone, and yeah we recommend the wsdl > first way. > > Freeman > －－－－－－－－－－－－－ > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://fusesource.com | http://www.redhat.com/ > Twitter: freemanfang > Blog: http://freemanfang.blogspot.com > http://blog.sina.com.cn/u/1473905042 > weibo: http://weibo.com/u/1473905042 > > On 2012-11-12, at 下午4:59, Gege wrote: > > > Thanks ! > > > > Just to be sure, since the callback is of type > > AsyncHandler<GreetMeSometimeResponse>, does that mean that the webservice > > must be created from WSDL, and not from Java ? > > > > That would be logical : i did not fount the @UseAsyncMethod anywhere. So > i > > started to code something on top of async @WebServiceProvider, do myself > je > > jaxb glue, and i was going to do some mapping between @WebServiceProvider > > and methods of a class. I had the same requirement that the WS must be > > created from WSDL. > > > > I guess CXF already did it for me. Good ! :-) > > > > > > 2012/11/12 Freeman Fang <[email protected]> > > > >> Hi, > >> > >> FYI, for the jaxws server side asynchronous, since CXF 2.6.x, you can > use > >> @UseAsyncMethod which will leverage CXF Continuations API underlying, > take > >> a look at jaxws_async sample(especially the README.txt which explain the > >> Server Side Asynchronous models) shipped with CXF 2.6.x kit to get more > >> details. > >> > >> Freeman > >> －－－－－－－－－－－－－ > >> Freeman(Yue) Fang > >> > >> Red Hat, Inc. > >> FuseSource is now part of Red Hat > >> Web: http://fusesource.com | http://www.redhat.com/ > >> Twitter: freemanfang > >> Blog: http://freemanfang.blogspot.com > >> http://blog.sina.com.cn/u/1473905042 > >> weibo: http://weibo.com/u/1473905042 > >> > >> On 2012-11-11, at 下午8:38, Gege wrote: > >> > >>> Hi, > >>> > >>> I'm using CXF between two endpoints (both are AS) in SOAP and/or REST > >> over > >>> HTTP. > >>> > >>> I want network callflows to be as simple as possible (no callbacks, > plain > >>> simple request/answer) and i want to be resources-efficient because > some > >>> requests might be long (and i'll have long-polling for events). > >>> > >>> So, I need to have asynchronous implementations (in java) of both > client > >>> and servers. > >>> > >>> Here is where i stand: > >>> > >>> SOAP (jax-ws) : > >>> - asynchronous client : OK (wsimport + binding.xml) > >>> - asynchronous server : not supported yet by CXF (AsyncProvider is > >>> specified in jax-ws 2.2, it's not the most simple to implement (handle > >> the > >>> XML myself...) but it should be able to do the job, might be supported > in > >>> jax-ws-ri by sun). > >>> > >>> REST (jax-rs) : > >>> - asynchronous client (cxf-wadl2java) : ? i did find anything about > >>> asynchronous client and I really hope someone can give me a pointer > >>> - asynchronous server : OK using AsyncResponse (jax-rs 2.0) and some > >> fixes > >>> that i'll post once i've tested a bit more > >>> > >>> For now, I feel like there are some pieces missing. > >>> Of course i could implement a REST client myself, but i feel it's a > >> waste. > >>> There are libraries and utilities everywhere and what I want to do > seems > >>> pretty much in the scope of jax-rs and jax-ws). > >>> > >>> Thanks in advance. > >> > >> > >
