Geert, I think I have solved the problem. When you asked me for the minimal example, I realized that I had never done that. I figured that my XSLs weren't too complicated so there was no need to reduce it to bare minimum.
So, I created a very simple example, and it worked! I then started adding more and more until I figured out what was causing the error. Turns out, I was including a third-party XSL to do some stuff and there was this line at the top: <xsl:output method="html" omit-xml-declaration="yes" indent="no"/> Simply removing this line got rid of the error. Why it caused the exception at that particular part of the identity template, I don't know, but I'm glad the issue is resolved. Thanks for you help, JF --- Geert Josten <[EMAIL PROTECTED]> wrote: > Can you give me the following > > 1) minimal XSL stylesheets > 2) minimal XML example > 3) relevant sitemap fragment > 4) Java build number (java -version) > > And any other relevant information. > > Can't promiss, but I will try to take a look. It is > always good to be > aware of bugs or common mistakes in XSL parsers and > Java/Cocoon setups.. > > Kind regards, > Geert > > > -----Oorspronkelijk bericht----- > > Van: footh [mailto:[EMAIL PROTECTED] > > Verzonden: vrijdag 9 februari 2007 19:28 > > Aan: [email protected] > > Onderwerp: RE: Unique XSL transform error that > only occurs > > with Cocoon and Java 1.5 > > > > Geert, thanks for the replies. > > > > I tried all your recommended changes and nothing > worked. I > > had xalan 2.7.0 in both the lib/endorsed dir of my > web > > container (using Tomcat) and the lib directory of > my web > > application. I tried various combinations (in one > dir, not > > the other, etc.) and nothing worked - still the > same > > transformer error. > > > > I also tried your stylesheet change and that had > no effect. > > I still receive the same errors. > > > > The baffling thing is I ran this template through > the xalan > > stylesheet command line utility under Java 1.5 and > it > > transformed fine. Also, if I switch my web app > environment > > to Java 1.4 it transforms fine. I have just run > out of > > options to debug this thing. I have no idea where > to start. > > > > Do you by any chance have a similar environment > set up where > > you could test the template to see if you get the > same error? > > > > Regards, > > > > JF > > > > > > --- Geert Josten <[EMAIL PROTECTED]> wrote: > > > > > 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 > === message truncated === ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
