list4xt : Mailing list for the XT users community.

[list4xt] More precise error location

User: Website

New Message
• Reply
• Next message: guy: "[list4xt] handling stylesheet errors"
• Previous message: James_Ma@i2.com: "[list4xt] Re: Using XT to process dynamically generated XML"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi there! ;)

I'm using XT from about a year and I think one of most annoying (and
most recurring, at least in my own stylesheets) errors of this XSL
processor is "cannot convert to node-set" (generated, I can guess, by
com.jclark.xsl.expr.VariantBase, line 8th). Surely is a significative
error, but it comes always with *no* line location information at all,
so it's extremely difficult to "guess" which is the "bad" code
(especially when you wrote many, many, many lines of XSL code one at a
time and test them as a whole). Is there a way to modify XT's source
code to include proper location info for this error as well for all
other errors, which already display xslfilename/errorline ?
Thanks!

P.S. I'm sorry if this is a FAQ... a "RTFM" ;) answer will be
appreciated, anyway.
---------------------------------------------------------------
\\//_ Live long and prosper and ... HAVE A GOOD TIME! ;-)
Lorenzo Gallucci - wes74@engineer.com - ICQ# 19194057
--- Wenn die Nacht am tiefsten ist, ist der Tag am nächsten ---

--
Mailing list for the XT users community.     (http://edgertonchamber.org)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)

• Next message: guy: "[list4xt] handling stylesheet errors"
• Previous message: James_Ma@i2.com: "[list4xt] Re: Using XT to process dynamically generated XML"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]