PM41696: INCORRECT DEFAULT NAMESPACE FOR ELEMENTS THAT CHANGED THEIR QNAMES AND CONFLICT WITH AN EXPLICIT DEFAULT DECLARATION

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• The explicit default namespace of an element that has changed
  its QName to contain a different default namespace mapping does
  not get updated to match the new internal default mapping.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the XML API for IBM WebSphere      *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Elements that changed their QNames to   *
  *                      conflict with an explicit default       *
  *                      declaration were in the wrong           *
  *                      namespace scope.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The explicit default namespace of an element that has changed
  its QName to contain a different default namespace mapping does
  not get updated to match the new internal default mapping.
  

Problem conclusion

• The explicit default namespace declaration now gets properly
  updated to match the new internal default mapping.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.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 is sysrouted FROM one or more of the following:

  PM23976

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY