> On Mar 20, 2019, at 4:26 AM, [email protected] wrote: > > I opened a question/bug in the CXF issue tracker, but did not have a response > within two months. Is the issue tracker still active?? Can you help me with > the questions posted there? > > Async binding not JAX-WS compliant > https://issues.apache.org/jira/browse/CXF-7951 > <https://issues.apache.org/jira/browse/CXF-7951>
Reading through the spec, you’re right. It does look like the CXF generated code is not correct. However, the. JAXWS TCK is obviously not testing it or we would have hit this issue long ago. That said, it’s also not something we’re likely to change anytime soon. That would be a completely backwards incompatible change that would likely affect a lot of CXF users. Certainly not something to be done in a patch release. The two options to consider for you: (that I can think of) 1) The CXF runtime MAY work with the wsimport generated code. I’m not really sure. In general, the CXF runtime is a bit more flexible and allows for some extra situations. Thus, it might just work if you use wsimport to generate the clients. Then again, it might not. :) I haven’t tested it. If it doesn’t work and you could create a test case for it, that could be something we could consider. If the runtime can be updated to detect and support both mappings, that’s something that potentially could be done. 2) Flip to bare style for that operation. If you use bare style, I believe the signatures should match between metro/cxf. -- Daniel Kulp [email protected] <mailto:[email protected]> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://talend.com <http://coders.talend.com/>
