WLS 10.3 Web Services - Inline namespace does not appear in response when deploying ear file from WLS 8.1 SP4. (Doc ID 1126776.1)

Last updated on JUNE 09, 2017

Applies to:

Oracle Weblogic Server - Version: 10.3 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

Weblogic Web Services - In-line Namespace doesn't appear in response when deploying ear file from 8.1SP4. In 8.1 web services, pre-8.1SP5, a SOAP response looks like:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Body>
<own:response-acme-owner-service xmlns:own="http://acme.com/someURI">
<own:transaction-id xmlns:own="http://acme.com/someURI">2344157</own:transaction-id>
<own:owner xmlns:own="http://acme.com/someURI">
<own:owner-number xmlns:own="http://acme.com/someURI">5451507</own:owner-number>
<own:account-number xmlns:own="http://acme.com/someURI">672138</own:account-number>
<own:owner-info xmlns:own="http://acme.com/someURI">
<own:first-name xmlns:own="http://acme.com/someURI">acme</own:first-name>
<own:address1 xmlns:own="http://acme.com/someURI">111 Parkway</own:address1>
.....

Note that the namespace is written out in each line.

In 8.1SP5 the response looks like:
<env:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<own:response-acme-owner-service xmlns:own="http://acme.com/someURI">
<own:transaction-id>2348352</own:transaction-id>
<own:owner>
<own:owner-number>6026705</own:owner-number>
<own:account-number>6</own:account-number>
<own:owner-info>
<own:first-name>acme</own:first-name>
<own:address1>111 Parkway</own:address1>
....

The format with the 'namespace in each line' is deprecated and instead the format should look like the second example.  However, there may be occurrences where a client still depends on the old format.  One such scenario where this could be a problem is if a customer has upgraded to a later version, such as WLS 10.3,  and directly deployed their WLS 8.1 SP4 application to the new Weblogic version. The response will now be different than it was in WLS 8.1 SP4 causing an issue if the client relies on the old behavior.

Changes

N/A

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms