PK66483: WEBSERVICES MAY NOT INTEROPERATE WITH OLDER VERSIONS OF MICROSOFT .NET

Fixes are available

APAR status

Closed as program error.

Error description

When a webservices consumer or provider is using a Web
Services Description Language (wsdl) with
elementFormDefault="unqualified", some elements in the SOAP
message are still qualified.  This can cause problems with
older versions of Microsoft .NET because they may be expecting
all elements in the body to be unqualified.

This is taking place because the .NET client or server has
trouble deserializing SOAP messages serialized by WebSphere V6.
The messages that .NET does not like contain prefixed elements
such as

<p123:helloWorld xmlns:p123="http://test.hello.world/">

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6 and V7  *
*                  users who have recently migrated from V5.1  *
*                  and whose JAX-RPC web services clients      *
*                  interoperate with older versions of .NET    *
*                  Web Service, and cannot update their        *
*                  existing web services.                      *
****************************************************************
* PROBLEM DESCRIPTION: A .NET server may fail to deserialize   *
*                      a child element sent from an            *
*                      Application Server v6 JAX-RPC web       *
*                      service client.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Older .NET Web Services may expect SOAP message payload
elements to be qualified using default namespaces ("payload
elements" refers to the child elements of the SOAP Body
element). But the Application Server v6 web services runtime
does not serialize qualified elements using default
namespaces; instead, it serializes qualified elements with
prefixes and namespace declarations.
Here's an example where a "name" element is qualified using a
default namespace:
<name xmlns="http://test.namespace/">John</name>
and one where "name" is qualified using prefixes and namespace
declarations:
<pre2:name xmlns:pre2="http://test.namespace/">John</pre2:name>
Older versions of .NET may have problems deserializing a SOAP
message containing prefixed payload elements. This is a .NET
limitation, since such a message is valid XML. This APAR tries
to accommodate this limitation.
This behavior was changed from the Application Server web
services V5.1 runtime, which qualifies elements with default
namespaces, not prefixes.

Problem conclusion

The JVM property
com.ibm.ws.webservices.serializeOperationElementUsingDef
aultNamespace was added to enable the JAX-RPC web services
runtime to serialize the topmost payload element--the one that
immediately follows the SOAP Body element--using a default
namespace declaration.

The APAR is applicable only for web services and web
services clients generated from document/literal/wrapped style
WSDLs.

In order for the APAR to be enabled, the property must be set
to "true". The property is set as a JVM Property.

For unmanaged Application Server web services clients, this can
be done via command line parameters in a command
window/console, as in the following example:

java
-Dcom.ibm.ws.webservices.serializeOperationElementUsingDefaultNa
mespace=true MyWebServiceClient

For managed web services clients and web services running in
the application server, the  property can be set via the
administrative console.

This would be accessed in a V6.1 console at:
Servers->Application Servers->myServerName->Java and
Process Management->Process Definition->Java Virtual
Machine->Custom Properties

Click "New" to create the new property and set "true" as
the value to enable it. A restart of the server is required
for the property to take effect.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.23, 6.0.2.33 and 7.0.0.1.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK66483
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-22
Closed date
2008-09-10
Last modified date
2012-03-23

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK66483: WEBSERVICES MAY NOT INTEROPERATE WITH OLDER VERSIONS OF MICROSOFT .NET

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?