JBoss EAP 6.3.0 SOAP (JAX WS) Request Body is missing at runtime when calling Oracle JAX WS

Solution Unverified - Updated -

Issue

When our Java code (soap client) invokes a SOAP API, the soap message does not contain the soap:body elements. Therefore, the soap client is unable to pass the parameters required for the API call which results in the soap server returning an error response.

The soap calls were working properly earlier (with JDK 1.6 and JBoss EAP 5.1.2). We are now migrating our JDK from 1.6 to 1.7 and our server from JBoss EAP 5.1.2 to JBoss EAP 6.3.

We believe the existing web service (Oracle JAX WS) implementation is not compatible with default JBoss Apache CSX-JAX-WS implementation.

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0

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.