Subject: AW: [xsl] <saxon-error-element/> From: Merico Raffaele <raffaele.merico@xxxxxxx> Date: Tue, 20 Jun 2006 15:01:48 +0200 |
Dear Michael Kay Thanks to your explanations below I have solved the problem. The error was caused by the usage of fn:node-name() without its newly mandatory argument. I discovered the bug when I executed the generation on the command line (this step is usually hidden as meta generation step). This showed me also, that I could have found the causing source without disturbing you. Many thanks for your generous support. Cheers Raffaele > -----Urspr|ngliche Nachricht----- > Von: Michael Kay [mailto:mike@xxxxxxxxxxxx] > Gesendet: Dienstag, 20. Juni 2006 10:41 > An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Betreff: RE: [xsl] <saxon-error-element/> > > 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.merico@xxxxxxx] > > Sent: 20 June 2006 08:40 > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > > 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Parsing problem + unknown, Michael Kay | Thread | [xsl] Avoid CSS, Bernie |
RE: [xsl] Parsing problem + unknown, Michael Kay | Date | RE: [xsl] Unique XSLT, Jacoby, Peter R. |
Month |