Swift XML Parser fails to validate DTD schemas if used in TIBCO IntegrationManager™ process.
Article ID: KB0088783
Updated On:
| Products | Versions |
|---|---|
| TIBCO IntegrationManager | - |
| Not Applicable | - |
Description
Description:
When the Swift XML Parser is used in the TIBCO IntegrationManager (IM) process as a plugin, it fails to validate DTD schemas and throws the error, "java.io.IOException: Error reading schema: TOKEN".
Symptoms:
The following error is seen on the console and/or in the Engine log file.
""java.io.IOException: Error reading schema: TOKEN".
Cause:
TIBCOxml.jar fails to validate DTD schemas and the xmlsdk.jar does not have the method "makeName" with two arguments.
When the Swift XML Parser is used in the TIBCO IntegrationManager (IM) process as a plugin, it fails to validate DTD schemas and throws the error, "java.io.IOException: Error reading schema: TOKEN".
Symptoms:
The following error is seen on the console and/or in the Engine log file.
""java.io.IOException: Error reading schema: TOKEN".
Cause:
TIBCOxml.jar fails to validate DTD schemas and the xmlsdk.jar does not have the method "makeName" with two arguments.
Issue/Introduction
Swift XML Parser fails to validate DTD schemas if used in TIBCO IntegrationManager™ process.
Resolution
This error is thrown if TIBCOxml.jar
(<tra-home>/lib) is placed before xmlsdk.jar
(<im-home>/java) in the extended path in the file (imed/imse .tra). The TIBCOxml.jar fails to validate DTD schemas used in the XML Parser.
However, if xmlsdk.jar is placed before TIBCOxml.jar then the validation
error disappears but throws "java.lang.NoSuchMethodError:
com.tibco.xml.data.primitive.ExpandedName.makeName(
Ljava/lang/String;Ljava/lang/String;)"
Workaround:
Use different (imed/imse .tra) files with one pointing to xmlsdk.jar in front (for the IM XML Parser process) and th other pointing to TIBCOxml.jar before (For SWIFT XML Parser process).
Use two (.cfg) files having the property "Config.Primary.Partition" with one pointing to the IM Parser JobCreator and the other pointing to the SWIFT Parser JobCreator to run the IM engine.
Ljava/lang/String;Ljava/lang/String;)"
Workaround:
Use different (imed/imse .tra) files with one pointing to xmlsdk.jar in front (for the IM XML Parser process) and th other pointing to TIBCOxml.jar before (For SWIFT XML Parser process).
Use two (.cfg) files having the property "Config.Primary.Partition" with one pointing to the IM Parser JobCreator and the other pointing to the SWIFT Parser JobCreator to run the IM engine.
Feedback
Yes
No
Powered by
