PM52936: NO ERROR DISPLAYED WITH XML ENCODING OTHER THAN UTF-8 WHEN IMPORTING USING XML CLASSIC IMPORTER

APAR status

• Closed as program error.

Error description

• XML Classic and Xerces importer supports only UTF-8 encoding on
  import. No error is displayed for other encodings when using
  the XML Classic Importer.
  

Local fix

• WTXCQ - WTX00039343
  GK / GK
  Circumvention: None
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender customers trying to import a
  schema that has an encoding other than UTF-8 using the Classic
  option
  
  Problem Description:
  Importing a schema that has an encoding other than UTF-8 but not
  included in the supported data languages using the Classic
  option will receive the error message: "The provided encoding:
  xxx is not currently supported."
  
  Platforms Affected:
  Windows
  

Problem conclusion

• Both Classic and Xerces schema importers should issue an error
  if the imported schema has an encoding that is not part of the
  supported data languages.
  Replaced in XmlSchemaImporter's importXmlSchema function the
  type of the SAXParser being instantiated - from
  com.ibm.websphere.dtx.xmlsimp.SAXParser to
  com.ibm.websphere.dtx.xmlsimp.SAXParser
  
  Delivered in:
  8.2.0.6, 8.3.0.5, 8.4.0.1
  

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

  WEBSPHERE LAUNC

• Fixed component ID

  5724M4011

Applicable component levels

• R820 PSY

     UP

• R830 PSY

     UP

• R840 PSY

     UP