JBoss JAX-WS CXF client generates broken XML with WRAPPED stub type in JBoss EAP 6.

Solution Unverified - Updated -

Issue

  • There are web services provided to the application in the form of a JAR with the stubs and a wsdl already mapped out.
    These JAR's and the local wsdl are referenced in the web.xml as follows:
 <service-ref>
      <service-ref-name>service/SampleWebService</service-ref-name>
      <service-interface>org.rogueware.ee.webservice.SampleWebService_Service</service-interface>
      <service-ref-type>org.rogueware.ee.webservice.SampleWebService_Service</service-ref-type>
      <service-qname xmlns:sb="http://webservice.ee.rogueware.org">sb:SampleWebService</service-qname>
   </service-ref>
  • It is noticed that some of the stubs methods are annotated as SOAPBinding.ParameterStyle.WRAPPER
    and not SOAPBinding.ParameterStyle.BARE. This causes the JBoss JAX-WS client CXF to generate totally broken XML for the SOAP payload when invoking a call. Why is the JBoss EAP JAX-WS implementation broken and what are the scenarios to cause the WRAPPER to be broken?

Environment

  • Red Hat Enterprise Application Platform (EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.