Migrating a TDI 7.0 assembly line containing the XSL based XML Parser may fail in later versions of TDI.

Technote (troubleshooting)


Problem(Abstract)


Tivoli Directory Integrator version 7.0 packaged the JVM (IBM 1.5) which had a default Transformer that would also accept "XML" in the output method. For example,

<XSL:stylesheet xmlns:XSL="http://www.w3.org/1999/XSL/Transform" version="1.0">
<XSL:output method="XML" indent="yes" />

In TDI 7.1, the packaged JVM (IBM 1.6) has a default Transformer which is more strict.

This is correct according to the XSL Transformation specifications.

Symptom

The following error is displayed in the ibmdi.log file:

CTGDIS810E handleException - cannot handle exception , initialize
javax.xml.transform.TransformerConfigurationException: com.ibm.xtq.xslt.jaxp.HandledRuntimeException:


[ERR 0512] Cannot continue because of stylesheet errors.

Executing from the command line would display


CTGDKD024I Remote API successfully started on port:1099, bound to:'SessionFactory'. SSL and Client Authentication are enabled.
Platform: 'Generic'

ERROR: '[ERR XS1016][ERR XTSE1570]

The 'method' attribute of the xsl:output element is 'XML' but it must be one of 'xml', 'html', 'text', or 'xhtml'.; SystemID: xsl; Line#: -1; Column#: -1'
FATAL ERROR: '[ERR 0512] Cannot continue because of stylesheet errors.'

Cause

In TDI 7.1 and TDI 7.1.1, the JVM's default Transformer does not accept the upper-case text in the output method.


java version "1.6.0"
Java(TM) SE Runtime Environment (build pwa6460sr7-20091215_02(SR7))


Environment

Tivoli Directory Integrator version 7.1

Diagnosing the problem


If the symptom above is displayed, then check the Parser input XSL definition for case sensitive definitions and make the appropriate modifications.


Example:

    <XSL:output method="XML" indent="yes" /> should be <XSL:output method="xml" indent="yes" />

This issue was seen during the upgrade of Lotus Connections 3 to 4 and migrating custom assembly lines from TDI 7.0 to 7.1.


NOTE: The 7.1 InfoCenter Reference Guide > Parsers Section contains an example that is incorrect in the birds.xml example. This has been corrected in the 7.1.1 version.


Resolving the problem

Change the Parser input XSL definitions that do not comply with the standard.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Security Directory Integrator
General

Software version:

7.1, 7.1.1

Operating system(s):

All Platforms

Reference #:

1621133

Modified date:

2013-08-23

Translate my page

Machine Translation

Content navigation