you may need to post your xsl. it's unclear from what you say below - if you comment out all transfomers, does the exception go away?
Geoff > -----Original Message----- > From: Don Saxton [mailto:[EMAIL PROTECTED] > Sent: Monday, March 31, 2003 9:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Failed to execute pipeline.: Errors in XSLT transformation > > > Thanks Charles. > I totally agree. and that is why I am stumped. To be sure the request is > filled beginning with a > <map:generate type="session-attr"> > which I <map:serialize type="xml"/> and save the result as p1.xml. > > THEN I test several xsl (just to be sure) on p1.xml. The xsl all > pass both > in xmlspy and xslerator. > > THEN removng the <map:serialize type="xml"/> and replacing with > one of the > tested xsl, <map:serialize type="xml"/> or <map:serialize > type="html"/> > (whichever is appropriate to the xsl) Still resutl in the bad voodoo > reported earlier. > > Incidentally looking at CachingStreamPipeline, I found the below > javadoc on > the class. Maybe if I switch cacheing off? how? > > The real blister is that I was so sure I was finished. > > Don > > * This stream pipeline is able to cache the response, if > * <ul> > * <li>a) the serializer is cacheable</li> > * <li>b) the <code>EventPipeline</code> is cacheable</li> > * </ul> > * > > ----- Original Message ----- > From: "Charles Yates" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, March 31, 2003 4:24 PM > Subject: Re: Failed to execute pipeline.: Errors in XSLT transformation > > > > In cases like this I do the following: > > > > 1) make sure the pipeline is giving the transformer in question the > > right input. (ie comment out the transformer and any subsequent ones and > > use XMLSerializer) > > 2) make sure the stylesheet works outside of cocoon. (you can do step > > one to get the appropriate input) > > > > Charles > > > > Don Saxton wrote: > > > > > I have tried several xsl and after double checking each of them I am > > > stumped. > > > > > > I found several zarros in bugzilla. In mail list I have seen several > > > "Failed to execute pipeline" and a couple related to NPE, but none > > > linking either to "Errors in XSLT". Worse these other msgs don't > > > indicate what solved the their problems. > > > > > > I am running 2.04 on w2k and I sure could use a clue. All classes > > > immediately surrounding the error are all cocoon. I have been > > > studiously avoiding 2.1 beta chaos. Is it now time to dive in? will > > > that help? > > > > > > Don > > > > > > > > > org.apache.cocoon.ProcessingException: Failed to execute pipeline.: > > > java.lang.RuntimeException: Errors in XSLT transformation: > > > Fatal: java.lang.NullPointerException > > > > > > > > > at > > > > org.apache.cocoon.components.pipeline.CachingStreamPipeline.proces > s(CachingS > treamPipeline.java:410) > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
