[
https://issues.jboss.org/browse/JBWS-3833?page=com.atlassian.jira.plugin....
]
Tadayoshi Sato commented on JBWS-3833:
--------------------------------------
Hi Jim,
Thank you for the input. In fact, I know that {{@UseAsyncMethod(always = true)}} forces
the async method to be invoked. The problem with this is that as explained in its source
code {{always = true}} option simply blocks threads to achieve pseudo-asynchronicity, so
it's not the true solution.
As Alessio pointed out, it turned out that what we really need is adding
{{<async-supported>true</async-supported>}} in {{web.xml}} so that
continuation is enabled for the servlet in JBoss.
@UseAsyncMethod doesn't seem to work on JBoss
---------------------------------------------
Key: JBWS-3833
URL:
https://issues.jboss.org/browse/JBWS-3833
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.3, jbossws-cxf-4.3.1
Reporter: Tadayoshi Sato
Assignee: Alessio Soldano
Attachments: async.zip
I developed the following WS endpoint that uses {{@UseAsyncMethod}}:
{code:java}
@WebService(...)
public class GreetingServiceImpl implements GreetingService {
...
@WebMethod
@UseAsyncMethod
public String hello(String name) { ... }
public Future<HelloResponse> helloAsync(final String name, final
AsyncHandler<HelloResponse> asyncHandler) { ... }
{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)