XSLT – Error Handing (Magic xpi 3.x)

The Magic xpi Server Flow Manager checks for errors during the execution of a step. If there is an error in an XSLT component step, the Error Handler is invoked and handles the error.

The first error in the step causes the termination of the step execution. If the step has multiple methods, and an error occurs in one of these methods, all subsequent methods are not executed.

The error codes for the XSLT component are listed below. You can also use Magic xpi's General Component Errors with the Directory Scanner component. The codes are returned to the Magic xpi Server in the Invocation program’s Error Code parameter.

The Java implementation might return exceptions when the operation fails. Most exceptions are generated from the core implementation. They are usually related to I/O operations or XSLT transformations, and to XML validity and syntax.

Java exception messages should be appended to the mapped error description.

Java exception types (instanceof) should be checked in the following order:

• org.apache.fop.apps.FOPException

• javax.xml.transform.TransformerException

• java.io.FileNotFoundException

• java.io.IOException

• com.magicsoftware.ibolt.commons.exception.IBRTException

• java.lang.Exception

Related Topics

Error Handling in Magic xpi