PM58128: MANUALLY CREATED XML ELEMENTS IN XML-SOAP CAN CAUSE NAMESPACE INCONSISTENCIES.

Fixes are available

APAR status

Closed as program error.

Error description

Using manually created XML Elements in an XML-Soap message could
cause Namespace inconsistencies in the final XML document. XML
Elements can be created by the createElementNS method using an
org.w3c.Element for example,

DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
DocumentBuilder builder;
try {
  builder = factory.newDocumentBuilder();
}
catch (Exception e) {
  throw new Exception("Exception happened.");
}
Document doc = builder.newDocument();
Element element = doc.createElementNS("anynamespace",
  "elementName");
element.setAttrute("xmlns:xsi",
  "http://www.w3.org/2001/XMLSchema-instance");
element.setAttribute("xmlns:somenamespace",
  "http://somenamespace/name");
####

In this case, WebSphere Application Server will send the invalid
XML-Soap without error or exception.  The XML problem with the
XML validity will be seen on the receiver of the XML-Soap
message.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server JAX-RPC webservices                  *
****************************************************************
* PROBLEM DESCRIPTION: Explicit prefix generation fails for    *
*                      wrapped elements in a SOAP response     *
*                      for JAX-RPC webservices                 *
****************************************************************
* RECOMMENDATION:  Apply fix pack containing the fix.          *
****************************************************************
In certain cases, when ElementFormDefault is set to qualified
in the WSDL, prefixes are not generated for wrapped elements.
This can cause SOAP validation to fail for JAX-RPC web
services clients.

Problem conclusion

This fix provides a mechanism to force generation of explicit
prefix's for such wrapped elements.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25 and 8.0.0.4.  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
PM58128
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-14
Closed date
2012-04-18
Last modified date
2012-06-26

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R800 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM58128: MANUALLY CREATED XML ELEMENTS IN XML-SOAP CAN CAUSE NAMESPACE INCONSISTENCIES.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R800 PSY

Document Information

Share your feedback

Need support?