After a closer look at this thread: My earlier reply should not apply to your case..
Have you tried: <xsl:apply-templates select="@*" /> <xsl:apply-templates select="node()" /> I have noticed strange behaviours before and ran into similar trouble with Cocoon recently. I recommend putting latest Xalan in the endorsed folder of your Cocoon/webserver environment and making sure no other versions of Xalan are in the classpath. Java 1.5 is shipped with a certain version of Xalan, of which I recall it not being the most stable version that has passed. I also noticed that Saxon.jar can cause conflicts, but only when multiple copies of the jar are loaded (e.g. one in web-inf/lib/ and one in lib/endorsed/ of jetty). Are there other XSL parser in your classpath? HTH, Geert > Drs. G.P.H. Josten Consultant Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 www.daidalos.nl KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. > Van: footh [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 8 februari 2007 23:27 > Aan: [email protected] > Onderwerp: Re: Unique XSL transform error that only occurs > with Cocoon and Java 1.5 > > I had done that and should've mentioned it on my first > message. The part that causes the error is the line: > > <xsl:apply-templates select="@*|node()" /> > > In particulary, the "select" piece. It doesn't like the > bar(|). If I get rid if it and only have either "@*" or > "node()" then I don't get the error. This is valid XSL, as I > said, the error only occurs when transforming with Cocoon and > Java 1.5. > > --- Bertrand Delacretaz <[EMAIL PROTECTED]> > wrote: > > > On 2/7/07, footh <[EMAIL PROTECTED]> wrote: > > > > > ...Does anyone have any suggestions about where I > > would > > > start looking to figure out what is going on?... > > > > If the exception gives no clue as to what's going wrong, I'd start > > commenting out parts of the transform to see exactly what > causes it to > > fail. > > > > -Bertrand > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > ______________________________________________________________ > ______________________ > Have a burning question? > Go to www.Answers.yahoo.com and get answers from real people who know. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
