PM09900: CALLING DOCUMENT() WITH NODE USES WRONG BASE URI

APAR status

• Closed as program error.

Error description

• If the document() function is invoked with a single argument
  that is a node,the node should be atomized, the result cast to
  xs:anyURI, and  resolved against the base URI of the node that
  appeared as the first argument.   It looks like XL TXE-J 2.0
  is resolving against the base URI from the static context
  instead, which should only happen for each item in the first
  argument  that is not a node.
  
  This affects conf_ver20 test docs10_025_01
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of the IBM WebSphere Application  *
  *                  Server v7.0 Feature Pack for XML 1.0        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Calling document() with node uses       *
  *                      wrong base URI                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  conf_ver20 test docs10_025_01 has expression:
  document(document('level1/level2/xreluri11b.xml')/*/filename)/*/
  body. Execution got error that can't find document
  ...docs/level3/xreluri09a.xml where the correct document is
  under .../docs/level1/level2/level3/xreluri09a.xml
  

Problem conclusion

• If the document() function is invoked with a single argument
  that is a node, the node should be atomized, the result cast to
  xs:anyURI, and resolved against the base URI of the node that
  appeared as the first argument. It looks like XL TXE-J 2.0 is
  resolving against the base URI from the static context instead,
  which should only happen for each item in the first argument
  that is not a node.
  
  To fix the problem, for document() function with a single
  argument, if the argument is a node, get the base URI from the
  argument node.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.0.5. 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:

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

Fix information

• Fixed component name

  XML FEATUREPACK

• Fixed component ID

  5724J0856

Applicable component levels

• R700 PSY

     UP