> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
...
> Next try was to get 2.0.3 and install it, this time using Xerces+Xalan
> right from the start.
> This resulted in:
> java.lang.NullPointerException
> at org.apache.cocoon.components.xslt.XSLTProcessorImpl
> .resolve(XSLTProcessorImpl.java:489)
> at org.apache.xpath.SourceTreeManager.resolveURI
> (SourceTreeManager.java:184)
> This was triggered by a document('cocoon://int/release-list') in
> the XSLT.
> What's really bad is that the exception appears to be rethrown right
> up to the tomcat level, which causes a partially generated HTML
> delivered to the browser and, worse, cached. No 500.
>
> The exception is caused because "includes" in the XSLTTransformerImpl
> is null. Apparently, this was implemented with the premise that
> only XSL includes will go through the method. Unfortunately, URLs
> for document() also go through this. Of course, the information
> should be used for caching the pipeline output.
>
> I quickly hacked a if(includes!=null) {} around the problem (should
> rather have setup something for cache validation for the pipeline...if
> I could only understand this!).
If you can, please create simple test case and send it to bugzilla.
Vadim
> Now, it runs...slowly, because of
> Xalan bug #2425.
> I ditched Xalan and use Saxon again, with Xerces. This is the current
> situation.
>
> J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
