You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Sam Coward <sa...@atnet.net.au> on 2003/06/05 08:33:47 UTC
... Bug 20494: Willing to help, but...
Hmm. I just posted bug 20494 which seemed to appear just after doing an
update which changed the xalan jar file to version 2.5.1. I also
attached to this bug a small example that reproduces the problem in the
standalone jetty + webapp produced by the build.
I'd really like to help look into this, but I just can't seem to obtain
the source for the excalibur xmlutil package where the errors seem to be
happening. No other messages are being logged to any of the logfiles in
WEB-INF/log (Stacktrace appended below if you're curious).
The avalon-excalibur/xmlutil code from CVS HEAD seems to contain
differences and will not compile against avalon-framework and logkit
jars from the current cocoon-2.1 CVS HEAD.
How do other developers deal with tracking down problems in these JARs?
Is there some place I can obtain the source used to build the
excalibur-xmlutil-20030520.jar file that is in cocoon-2.1 CVS HEAD
currently?
Am I even looking at the right place to try and find the problem? Or is
this error message the by-product of some other hidden exception that
has been lost?
regards,
Sam
exception follows:
---snip---
Original Exception:
org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in
creating Transform Handler
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:380)
at
org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:302)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:391)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:672)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:505)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:467)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:150)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:162)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:325)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:133)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:162)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:325)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
at org.apache.cocoon.Cocoon.process(Cocoon.java:626)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1083)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
Caused by: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable
to create templates for stylesheet:
file:/usr/src/cocoon-2.1/build/webapp/test/simple-transform.xml
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
... 39 more
Original Exception:
org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to create
templates for stylesheet:
file:/usr/src/cocoon-2.1/build/webapp/test/simple-transform.xml
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
at
org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:302)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:391)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:672)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:505)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:467)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:150)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:162)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:325)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:133)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:162)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:325)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
at org.apache.cocoon.Cocoon.process(Cocoon.java:626)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1083)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
Re: ... Bug 20494: Willing to help, but...
Posted by Sam Coward <sa...@atnet.net.au>.
Excellent, thanks!
I went around in circles for a while though because of the error
handling related to this - in fact my test was bad - the second xsl in
the attachment that was being included had xml extension instead of xsl
extension, but the exception and stacktrace didn't show the underlying
FileNotFoundException from FileSource! Thanks for the tip
Joerg Heinicke wrote:
> Hello Sam,
>
> what was your Xalan version before the update, so what was the working
> version? Do you have multiple step includes (stylesheet1 includes
> stylesheet2, that includes stylesheet3)? We already have a bug related
> to this: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20308.
>
> You can switch the transformer to Xalan to get your stylesheets
> working again.
>
> Joerg
>
> Sam Coward wrote:
>
>> Hmm. I just posted bug 20494 which seemed to appear just after doing
>> an update which changed the xalan jar file to version 2.5.1. I also
>> attached to this bug a small example that reproduces the problem in
>> the standalone jetty + webapp produced by the build.
>>
>> I'd really like to help look into this, but I just can't seem to
>> obtain the source for the excalibur xmlutil package where the errors
>> seem to be happening. No other messages are being logged to any of
>> the logfiles in WEB-INF/log (Stacktrace appended below if you're
>> curious).
>>
>> The avalon-excalibur/xmlutil code from CVS HEAD seems to contain
>> differences and will not compile against avalon-framework and logkit
>> jars from the current cocoon-2.1 CVS HEAD.
>>
>> How do other developers deal with tracking down problems in these
>> JARs? Is there some place I can obtain the source used to build the
>> excalibur-xmlutil-20030520.jar file that is in cocoon-2.1 CVS HEAD
>> currently?
>>
>> Am I even looking at the right place to try and find the problem? Or
>> is this error message the by-product of some other hidden exception
>> that has been lost?
>>
>> regards,
>> Sam
>>
>> exception follows:
>
>
> ...
>
>> Original Exception:
>> org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to
>> create templates for stylesheet:
>> file:/usr/src/cocoon-2.1/build/webapp/test/simple-transform.xml
>> at
>> org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
>>
>> at
>> org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:302)
>>
>
>
>
Re: ... Bug 20494: Willing to help, but...
Posted by Joerg Heinicke <jo...@gmx.de>.
Hello Sam,
what was your Xalan version before the update, so what was the working
version? Do you have multiple step includes (stylesheet1 includes
stylesheet2, that includes stylesheet3)? We already have a bug related
to this: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20308.
You can switch the transformer to Xalan to get your stylesheets working
again.
Joerg
Sam Coward wrote:
> Hmm. I just posted bug 20494 which seemed to appear just after doing an
> update which changed the xalan jar file to version 2.5.1. I also
> attached to this bug a small example that reproduces the problem in the
> standalone jetty + webapp produced by the build.
>
> I'd really like to help look into this, but I just can't seem to obtain
> the source for the excalibur xmlutil package where the errors seem to be
> happening. No other messages are being logged to any of the logfiles in
> WEB-INF/log (Stacktrace appended below if you're curious).
>
> The avalon-excalibur/xmlutil code from CVS HEAD seems to contain
> differences and will not compile against avalon-framework and logkit
> jars from the current cocoon-2.1 CVS HEAD.
>
> How do other developers deal with tracking down problems in these JARs?
> Is there some place I can obtain the source used to build the
> excalibur-xmlutil-20030520.jar file that is in cocoon-2.1 CVS HEAD
> currently?
>
> Am I even looking at the right place to try and find the problem? Or is
> this error message the by-product of some other hidden exception that
> has been lost?
>
> regards,
> Sam
>
> exception follows:
...
> Original Exception:
> org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to create
> templates for stylesheet:
> file:/usr/src/cocoon-2.1/build/webapp/test/simple-transform.xml
> at
> org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
>
> at
> org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:302)