This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Better Error Handling with XSL


I have a template file (StringUtils.XSL) which contains templates on how to
format phone numbers, parse SSN's, etc.  In my main XSL document i imported
it at follows:
<xsl:import href="StringUtils.XSL"/>.  My first few attempts failed and i
recieved the error - "The system cannot locate the object specified".  It
didn't take me too long to figure out what was wrong - i didn't specify the
correct directory for StringUtils.xsl.  Does anyone know how i can tell IE
to return more helpful errors?  or is there an error handler that i can
apply to the XSL parser?   Currently, IE returns the line number in the asp
were i call the transformNode function - this is not helpful.  also for
arguments sake what if i had 10 files imported - it would be helpful to know
which file was causing my problem.

thanks.
jibran


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]