You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Richard In Public <ed...@blueyonder.co.uk> on 2003/05/20 15:35:57 UTC
xsl:include chain trouble
Hi
The last stage of my HTML pipeline calls a XSL stylesheet which is
linked, via xsl:include to 2 other stylesheets, each of which link to
several more. I have been using this arrangement for some time now
without any problems.
I've just copied a project from my Windows machine to a linux box on
which I have a virtually-hosted account. Now I get the (unhelpful)
exception (see below) complaining
Usually this means either that the stylesheet cannot be found or that
the xsl is invalid. If I comment out all of the includes it works. If
leave in the first 'level' of includes it still works. The includes
from 'level 2' to 'level 3' cause the problem. All the stylsheets are
in the same directory so I cannot imagine that only some of the
stylesheets cannot be found. Commenting out the contents of the
stylesheet (apart from the very basics) doesn't help either, so I don't
appear to be dealing with invalid xsl.
Anyone have any ideas?
Richard Hoberman
cause: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to
create templates for stylesheet:
file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
full exception chain stacktrace[hide]
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:671)
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.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:640) at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1139) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
at java.lang.Thread.run(Thread.java:536)Caused by:
org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to create
templates for stylesheet:
file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
... 57 more
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble
Posted by Richard In Public <ed...@blueyonder.co.uk>.
Hi Joerg
I'm using Xalan. Sorry, forgot to mention that.
Richard
Joerg Heinicke wrote:
> Are you using XSLTC or Xalan? XSLTC does not resolve relative paths
> correctly.
>
> Joerg
>
> Richard In Public wrote:
>
>> Hi
>>
>> The last stage of my HTML pipeline calls a XSL stylesheet which is
>> linked, via xsl:include to 2 other stylesheets, each of which link to
>> several more. I have been using this arrangement for some time now
>> without any problems.
>>
>> I've just copied a project from my Windows machine to a linux box on
>> which I have a virtually-hosted account. Now I get the (unhelpful)
>> exception (see below) complaining
>>
>> Usually this means either that the stylesheet cannot be found or that
>> the xsl is invalid. If I comment out all of the includes it works.
>> If leave in the first 'level' of includes it still works. The
>> includes from 'level 2' to 'level 3' cause the problem. All the
>> stylsheets are in the same directory so I cannot imagine that only
>> some of the stylesheets cannot be found. Commenting out the contents
>> of the stylesheet (apart from the very basics) doesn't help either, so
>> I don't appear to be dealing with invalid xsl.
>>
>> Anyone have any ideas?
>>
>> Richard Hoberman
>>
>>
>> cause: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to
>> create templates for stylesheet:
>> file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
>>
>>
>> full exception chain stacktrace[hide]
>>
>> 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)
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble (with XSLTC)
Posted by leo leonid <te...@leonid.de>.
On Dienstag, Mai 20, 2003, at 09:29 Uhr, Joerg Heinicke wrote:
> leo leonid wrote:
>>> Are you using XSLTC or Xalan? XSLTC does not resolve relative paths
>>> correctly.
>>>
>>> Joerg
>> Thats exactly the problem I run into when migrating my projects to
>> C2.1 with XSLTC as default.
>> Is there a solution other than to switch back to Xalan?
>> /Leo
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17825
>
OK. Thanks for confirming this.
> The question is whether it's a bug of Cocoon or XSLTC. I guess the
> second, but it's still assigned to Cocoon team, not Xalan. Can anybody
> confirm my guess (therefore cc-ing cocoon-dev)?
>
> And a solution? Not at the moment. Only "forcing" developers to fix
> the bug. (It's already marked as blocker, but it does not prevent us
> from releasing new Cocoon versions :-) )
>
Right, but maybe it's worth a note in an Upgrade-How-To (I thought
there was a wiki-page or even a page in the docs on this topic but
couldn't find it anymore). Also worth a note are all namespace changes
(e.g. i18n).
Thanks
/Leo
> Joerg
>
> --
>
> System Development
> VIRBUS AG
> Fon +49(0)341-979-7419
> Fax +49(0)341-979-7409
> joerg.heinicke@virbus.de
> www.virbus.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble (with XSLTC)
Posted by Joerg Heinicke <jo...@gmx.de>.
leo leonid wrote:
>> Are you using XSLTC or Xalan? XSLTC does not resolve relative paths
>> correctly.
>>
>> Joerg
>
> Thats exactly the problem I run into when migrating my projects to C2.1
> with XSLTC as default.
> Is there a solution other than to switch back to Xalan?
>
> /Leo
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17825
The question is whether it's a bug of Cocoon or XSLTC. I guess the second,
but it's still assigned to Cocoon team, not Xalan. Can anybody confirm my
guess (therefore cc-ing cocoon-dev)?
And a solution? Not at the moment. Only "forcing" developers to fix the bug.
(It's already marked as blocker, but it does not prevent us from releasing
new Cocoon versions :-) )
Joerg
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
Re: xsl:include chain trouble (with XSLTC)
Posted by Joerg Heinicke <jo...@gmx.de>.
leo leonid wrote:
>> Are you using XSLTC or Xalan? XSLTC does not resolve relative paths
>> correctly.
>>
>> Joerg
>
> Thats exactly the problem I run into when migrating my projects to C2.1
> with XSLTC as default.
> Is there a solution other than to switch back to Xalan?
>
> /Leo
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17825
The question is whether it's a bug of Cocoon or XSLTC. I guess the second,
but it's still assigned to Cocoon team, not Xalan. Can anybody confirm my
guess (therefore cc-ing cocoon-dev)?
And a solution? Not at the moment. Only "forcing" developers to fix the bug.
(It's already marked as blocker, but it does not prevent us from releasing
new Cocoon versions :-) )
Joerg
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble (with XSLTC)
Posted by leo leonid <te...@leonid.de>.
On Dienstag, Mai 20, 2003, at 06:44 Uhr, Joerg Heinicke wrote:
> Are you using XSLTC or Xalan? XSLTC does not resolve relative paths
> correctly.
>
> Joerg
>
<snip>
Thats exactly the problem I run into when migrating my projects to C2.1
with XSLTC as default.
Is there a solution other than to switch back to Xalan?
/Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble
Posted by Joerg Heinicke <jo...@gmx.de>.
Are you using XSLTC or Xalan? XSLTC does not resolve relative paths correctly.
Joerg
Richard In Public wrote:
> Hi
>
> The last stage of my HTML pipeline calls a XSL stylesheet which is
> linked, via xsl:include to 2 other stylesheets, each of which link to
> several more. I have been using this arrangement for some time now
> without any problems.
>
> I've just copied a project from my Windows machine to a linux box on
> which I have a virtually-hosted account. Now I get the (unhelpful)
> exception (see below) complaining
>
> Usually this means either that the stylesheet cannot be found or that
> the xsl is invalid. If I comment out all of the includes it works. If
> leave in the first 'level' of includes it still works. The includes
> from 'level 2' to 'level 3' cause the problem. All the stylsheets are
> in the same directory so I cannot imagine that only some of the
> stylesheets cannot be found. Commenting out the contents of the
> stylesheet (apart from the very basics) doesn't help either, so I don't
> appear to be dealing with invalid xsl.
>
> Anyone have any ideas?
>
> Richard Hoberman
>
>
> cause: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to
> create templates for stylesheet:
> file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
>
>
> full exception chain stacktrace[hide]
>
> 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)
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
RE: xsl:include chain trouble
Posted by Robert Koberg <ro...@koberg.com>.
Hi,
>From your original stack trace, it does not look like Xalan in doing the
resolving:
Original Exception:
> org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in
> creating Transform Handler at
> org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerA
> ndValidity(XSLTProcessorImpl.java:380)
> at
> org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer
> .java:302)
Perhaps the resolver being used is in or called from
o.a.c.transformation.TraxTransformer?
Is there some debug you can do to see the href and base arguments that are
being sent to the resolver? Most likely it is not using the correct base.
Best,
-Rob
> -----Original Message-----
> From: Richard In Public [mailto:edification@blueyonder.co.uk]
> Sent: Tuesday, May 20, 2003 7:31 AM
> To: cocoon-users@xml.apache.org
>
> Hi Andreas
>
> I had a delighful moment of hope after reading your response, but that
> doesn't appear to be the problem. Would have been nice...
>
> Thanks,
>
> Richard
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble
Posted by Richard In Public <ed...@blueyonder.co.uk>.
Hi Andreas
I had a delighful moment of hope after reading your response, but that
doesn't appear to be the problem. Would have been nice...
Thanks,
Richard
Andreas Hartmann wrote:
> Hi Richard,
>
> sorry if that's a stupid answer - could it be a filesystem-specific
> error (e.g., case sensitivity)?
>
> Andreas
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: xsl:include chain trouble
Posted by Andreas Hartmann <an...@apache.org>.
Hi Richard,
sorry if that's a stupid answer - could it be a filesystem-specific
error (e.g., case sensitivity)?
Andreas
Richard In Public wrote:
> Hi
>
> The last stage of my HTML pipeline calls a XSL stylesheet which is
> linked, via xsl:include to 2 other stylesheets, each of which link to
> several more. I have been using this arrangement for some time now
> without any problems.
>
> I've just copied a project from my Windows machine to a linux box on
> which I have a virtually-hosted account. Now I get the (unhelpful)
> exception (see below) complaining
>
> Usually this means either that the stylesheet cannot be found or that
> the xsl is invalid. If I comment out all of the includes it works. If
> leave in the first 'level' of includes it still works. The includes
> from 'level 2' to 'level 3' cause the problem. All the stylsheets are
> in the same directory so I cannot imagine that only some of the
> stylesheets cannot be found. Commenting out the contents of the
> stylesheet (apart from the very basics) doesn't help either, so I don't
> appear to be dealing with invalid xsl.
>
> Anyone have any ideas?
>
> Richard Hoberman
>
>
> cause: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to
> create templates for stylesheet:
> file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
>
>
> full exception chain stacktrace[hide]
>
> 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:671)
> 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.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:640) at
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
> at
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
> at
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
> at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
> at java.lang.Thread.run(Thread.java:536)Caused by:
> org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to create
> templates for stylesheet:
> file:/home1/r/rhoberma/public_html/cocoon/portal/src/skins/clear/xsl/page.xsl
> at
> org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:320)
> ... 57 more
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org