Please submit your problem to the saxon-help mailing list or forum at
http://sourceforge.net/projects/saxon
Include your stylesheet and source document: I'm not going to trawl through
mailing list archives to find them! It's also sometimes necessary to know
how the transformation was invoked.
I haven't seen <saxon-error-element> appear in visible output before. It's
used as a substitute name when you call xsl:element with an invalid QName as
the element name, but only after generating an error message which should
ensure that the compiled stylesheet is not generated.
It's worth checking the change log when you move to a new Saxon release.
There are often small changes that you need to be aware of, for example
changing namespaces in response to new versions of the W3C specifications.
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Merico Raffaele [mailto:raffaele(_dot_)merico(_at_)less(_dot_)ch]
Sent: 20 June 2006 08:40
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] <saxon-error-element/>
Dear Michael Kay
I tried to run XSLTg (an XSLT script, Mail on this list from
January, 12th
2006) with SaxonB-8.7.3. Until today I used XSLTg with
SaxonB-8.6 and lower, and it worked perfectly :-)
Now, the execution of XSLTg with SaxonB-8.7.3 produces a lot
of <saxon-error-element/> in the generated XSLT script. I
tried to find out what causes them but I could not find it
out. Any help would be much appreciated.
Many thanks in advance
Raffaele
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--