PM62827: DOM ELEMENT NODES RETURNED FROM JAXB MAY NOT HAVE A PARENT DOCUMENT NODE

Fixes are available

APAR status

Closed as program error.

Error description

DOM Element nodes returned from the IBM JAXB Unmarshaller may
not have a parent Document node. This can cause the evaluation
of XPath expressions such as "/a/b" to return no results.

Local fix

Issue can be avoided by re-writing their XPath expression
to "self::node()[local-name() = 'Test' and namespace-uri() =
'']/A",using the context node instead of walking back to the
document root.

This works on the result from both JAXB implementations and
so would allow the customer's application to run without setting
"com.ibm.xml.xlxp.jaxb.opti.level=0"

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server users  *
*                  of JAXB and JAX-WS.                         *
****************************************************************
* PROBLEM DESCRIPTION: DOM Element nodes constructed by the    *
*                      IBM JAXB runtime may have not have a    *
*                      parent Document node.                   *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this       *
*                  APAR.                                       *
****************************************************************
DOM Element nodes returned from the IBM JAXB Unmarshaller may
not have a parent Document node. This can cause the evaluation
of XPath expressions such as "/a/b" to return no results.

Problem conclusion

For compatibility with the JAXB reference implementation, the
IBM JAXB Unmarshaller was fixed so that each DOM Element node
it constructs is attached to its parent Document node.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.4 and 8.5.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
PM62827
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-19
Closed date
2012-05-15
Last modified date
2012-05-15

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 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

PM62827: DOM ELEMENT NODES RETURNED FROM JAXB MAY NOT HAVE A PARENT DOCUMENT NODE

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?