A correction to Joe's note. For the Process command line, you should use
the -EDUMP option to display the stack trace.
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
Joseph
Kesselman/Watson/ To: "Martin" <[EMAIL
PROTECTED]>
[EMAIL PROTECTED] cc: <[EMAIL
PROTECTED]>
Subject: Re:
TransformationExceptions
11/21/2002 09:00
AM
>How do I debug a TransformationException?
First, look at the exception's message field; that will generally provide
some indication of what failed.
If that isn't enough, "unwrap" the exception to get details on where the
failure occurred. If you're using the Process (command-line) driver for
Xalan, you can add the -DIAG option to request this detailed reporting; if
you're calling Xalan's APIs, look at Process's source code for an
illustration of how to obtain that information.
If that still doesn't provide enough information, post the details of the
exception's message, stack trace, and what you were trying to do --
preferably with a minimal example that we can use to reproduce the problem
-- and we'll try to provide guidance.
______________________________________
Joe Kesselman / IBM Research
