This is actually a server side issue, not a client side issue. The client is doing the correct thing. Per spec, it has to wait for the 200/202 response codes to make sure the message was successfully sent. However, the server wasn't sending the code back until after the invoke. I'm testing some fixes now, but I'm now running into some test failures in ws-rm with these changes. That's going to require some more digging.
Dan On Thu February 12 2009 11:48:27 am Daniel Kulp wrote: > On Wed February 11 2009 7:27:47 am hairman wrote: > > I'm trying to use the @Oneway-Annotation in a CXF Serviceinterface using > > Spring. @OneWay (camelCase) doesn't exist, so I think, it's a fault in > > the CXF docu? ( > > http://cwiki.apache.org/CXF20DOC/developing-a-service.html#DevelopingaSer > >vi ce-the%257b%2...@oneway%257d%257dannotation ) > > Yep. I've corrected that. Thanks! > > > I import javax.jws.Oneway, however the annotation seems to be ignored?! > > Hmmm.. that's definitely a bug. I can reproduce it here as well. Not > sure what's going on there yet. Digging into it now. > > Dan > > > /************************ WS-Interface > > **************************************/ > > WebService(name = "LockService", targetNamespace = "foo") > > public interface LockService { > > > > @WebMethod() > > @Oneway() > > public void oneWayTest(); > > } > > > > /************************** WS-Impl > > ***************************************/ public class LockServiceImpl > > implements LockService { > > public void oneWayTest() { > > try { > > Thread.sleep(4000); > > } catch (InterruptedException e) { > > System.out.println("+++++++++ Interrupted exception"); > > } > > } > > /***************************** Spring-Config > > *********************************/ > > <!-- Bean --> > > <bean id="lockService" class="foo.service.LockServiceImpl"/> > > > > <!-- Endpoints --> > > <jaxws:endpoint id="lockServiceEndpoint" implementor="#lockService" > > address="/LockService" /> > > > > The WS-Client still waits 4sec until he returns... -- Daniel Kulp [email protected] http://www.dankulp.com/blog
