Hi, André. André Mercadier <[EMAIL PROTECTED]> wrote on 2007-11-07 01:04:36 PM: [HZ: Deleted stylesheet.] > There is a newby error, and when I run it with any xml files, I get > this message : > > (Emplacement inconnu de l'erreur)Erreur XSLT (javax.xml.transform. > TransformerConfigurationException) > : Failed to compile stylesheet. 1 error detected. > Exception in thread "main" java.lang.RuntimeException: Failed to > compile stylesheet. 1 error detected. > at org.apache.xalan.xslt.Process.doExit(Process.java:1153) > at org.apache.xalan.xslt.Process.main(Process.java:1126) > > I'm sad, because there is no information about the error or its location. > > > But when I change the stylesheet version <xsl:stylesheet version="1. > 0">, I get this very useful message : > > file:/F:/FE_G7R3/Moteur/webApp/commun/xsl/bad.xsl; Ligne #4; Colonne > #-1; Erreur XSLT (javax.xml.tra > nsform.TransformerConfigurationException): No template exists named missing > Exception in thread "main" java.lang.RuntimeException: No template > exists named missing > at org.apache.xalan.xslt.Process.doExit(Process.java:1153) > at org.apache.xalan.xslt.Process.main(Process.java:1126)
The error messages you're showing appear to be messages produced by the Saxon XSLT processor. The Xalan-J Process command will, by default, use the default XSLT processor that's available on your class path, and if that happens to be Saxon, it will attempt to use Saxon. You should probably report the difference in error messages there. > All my project's stylesheets are 1.1. > Can I change to 1.0 without consequences ? That depends upon whether your stylesheets are actually using features that were proposed for inclusion in the draft XSLT 1.1. In some cases, there might be equivalent (though perhaps less convenient) features of XSLT 1.0 that you could use. Thanks, Henry ------------------------------------------------------------------ Henry Zongaro XSLT Processors Development IBM SWS Toronto Lab T/L 313-6044; Phone +1 905 413-6044 mailto:[EMAIL PROTECTED]
