[jira] [Created] (CXF-7951) Async binding not JAX-WS compliant

["Aritz Bastida (JIRA)" <ji...@apache.org>]

Aritz Bastida created CXF-7951:
----------------------------------

             Summary: Async binding not JAX-WS compliant
                 Key: CXF-7951
                 URL: https://issues.apache.org/jira/browse/CXF-7951
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 3.2.6
            Reporter: Aritz Bastida


According to JAX-WS 2.3 spec, section 2.3.4.3, the async binding differs from the sync binding in the handling of in-out and out parameters, namely:
 * No Holder class is used
 * Out parts or wrapper childs are gathered as properties in an ebtity called RespobseBean.

Personally, I don't understand this requirement because this results in a different method signature. But for some reason that' what the spec days...

In our project we are deploying our our services in Weblogic, which includes Metro (JAX-WS RI) as JAX-WS implementation. And that requires the above signature for the async binding to work.

However, CXF does not behave the same way: it expects the exact same same signature in both cases, just differring in the response type and name ("Async" suffix).

To put you in context, we are using Document/Literal Bare style in our clients, with four parts:
 * "request": IN 
 * "response": OUT
 * "cabecera": IN-OUT header=true
 * "metadatos": IN-OUT header=true

So, for the sync binding we have three method parameters, the last two wrapped by Holders. That same signature works in tthe async style, but Weblogic/JAX-WS RI doesn't like it...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)