Created attachment 941359 [details] reproducer +++ This bug was initially created as a clone of Bug #1146764 +++ Description of problem: Platform BZ for https://issues.jboss.org/browse/JBWS-3833 I developed the following WS endpoint that uses @UseAsyncMethod: @WebService(...) public class GreetingServiceImpl implements GreetingService { ... @WebMethod @UseAsyncMethod public String hello(String name) { ... } public Future<HelloResponse> helloAsync(final String name, final AsyncHandler<HelloResponse> asyncHandler) { ... } My expectation with @UseAsyncMethod is that whenever the hello() operation is invoked helloAsync() is eventually executed on JBoss (WildFly 8 or EAP 6). However, it really is not. I tested the same endpoint by launching it using Endpoint.publish(...) as well and it works as expected, so I don't think it's an issue with CXF itself but with JBoss WS integration. Attached please see the complete reproducer project async.zip for detail. Version-Release number of selected component (if applicable): JBoss WS CXF How reproducible: 100% Steps to Reproduce: 1. Deploy the reproducer (async.zip). 2. Invoke the 'hello' operation from SoapUI or any other WS client. 3. Check the server log. Actual results: You'll see the following message in the server log: INFO [com.redhat.samples.ws.GreetingServiceImpl] (default task-13) Hello, SoapUI! (SYNC) Expected results: The following message should be seen in the server log instead: INFO [com.redhat.samples.ws.GreetingServiceImpl] (default task-13) Hello, SoapUI! (ASYNC)
Alessio Soldano <asoldano> updated the status of jira JBWS-3833 to Resolved
Closed the ticket as it's not a bug.
Alessio Soldano <asoldano> updated the status of jira JBWS-3833 to Closed