IV23780: XML TRANSFORMATION FAILED WITH ERROR MESSAGE SAYING CAN'T FIND T HE DTD FILE

APAR status

• Closed as program error.

Error description

• Error Message: Xml transformation failed with below error.
  <OSB>5/22/12 13:34:16:630 GMT<CSB> 0000002d SystemErr R FATAL
  ERROR:
  'com.ibm.xml.xlxp.api.util.IOExceptionWrapper:
  /etc/opt/WebSphere/v700/profiles/ISAACCell/ISAAC/SwPrimitive.dtd
  (No such file or directory)'
  .
  Stack Trace: Error received:Xml transformation failed with below
  error.
  <OSB>5/22/12 13:34:16:630 GMT<CSB> 0000002d SystemErr R FATAL
  ERROR:
  'com.ibm.xml.xlxp.api.util.IOExceptionWrapper:
  /etc/opt/WebSphere/v700/profiles/ISAACCell/ISAAC/SwPrimitive.dtd
  (No such file or directory)'
  :/etc/opt/WebSphere/v700/profiles/ISAACCell/ISAAC/SwPrimitive.dt
  d (No such file or directory)
  <OSB>5/22/12 13:34:16:632 GMT<CSB> 0000002d SystemErr R FATAL
  ERROR:
  'com.ibm.xtq.common.utils.WrappedRuntimeException: An invalid
  XML character (Unicode: 0xffffffff) was found in the
  prolog of the document.'
           :An invalid XML character (Unicode: 0xffffffff)
  wasfound in the prolog of the document.
  .
  N/A
  

Local fix

• N/A
  

Problem summary

• Using JAXP API, transformation failed when using a StreamSource
  created with both Reader and system identifier are set.
  

Problem conclusion

• XLTXE1.0 code checks the StreamSource first for an InputStream,
  then a SystemId (interpreted as a URI), and finally a Reader.
  So, if the SystemId is set, the code ignores the Reader and
  instead load from the URI. According to JavaDoc for
  StreamSource.setSystemId() has: "The system identifier is
  optional if there is a byte stream or a character stream, but it
  is still useful to provide one, since the application can use it
  to resolve relative URIs and can include it in error messages
  and warnings (the parser will attempt to open a connection to
  the URI only if there is no byte stream or character stream
  specified). "
  The code should check for InputStream and Reader before trying
  to load from URI.
  .
  This defect will be fixed in:
  6.0.0 SR12
  6.0.1 SR4
  7.0.0 SR3
  

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/XSL

• Fixed component ID

  620700126

Applicable component levels

• R600 PSN

     UP

• R700 PSN

     UP