You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Irving Salisbury <ir...@dotech.com> on 2003/03/20 02:45:35 UTC
Weird exception
We are trying to get pdf stuff working on one of our apps. It works
great on our development machine, but our production machine gives the
following error (which I have pulled from the sitemap.xmap file). I am
happy to send more info, but thought maybe someone could at least point
me in the right direction of where I should be looking. I haven't seen
this cocoon error before:
DEBUG (2003-03-19) 18:38.21:656 [sitemap.transformer.xslt]
(/medicaid/pdf) HttpProcessor[80][2]/TraxTransformer: Using stylesheet:
'file:/Volumes/pkgs/jboss-3.0.4_tomcat-4.1.12/server/default/deploy/medicaid.war/xslt/reportFO.xsl'
in org.apache.cocoon.transformation.TraxTransformer@d38976, last
modified: 1048116553000
INFO (2003-03-19) 18:38.21:854 [sitemap] (/medicaid/pdf)
HttpProcessor[80][2]/PipelineNode: Error while processing pipeline at
file:/Volumes/pkgs/jboss-3.0.4_tomcat-4.1.12/server/default/deploy/medicaid.war/project.xmap:22:-1
org.apache.cocoon.ProcessingException: Exception in creating Transform
Handler: java.util.NoSuchElementException
at
org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransformerHandler(XSLTProcessorImpl.java:300)
at
org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransformerHandler(XSLTProcessorImpl.java:239)
at
org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:310)
at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.setupPipeline(AbstractEventPipeline.java:215)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.setup(CachingEventPipeline.java:278)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.generateKey(CachingEventPipeline.java:141)
at
org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:313)
at
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:154)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:85)
at
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:158)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:85)
at
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:166)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:109)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:151)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:109)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:145)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:332)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:124)
The weird thing is the line number for the xmap file, which points to
the start of the pipelines section. All other pipelines in the file
work fine, except this one. Like I said, the only thing unusual about
this particular pipeline is that we are trying to use the FOPSerializer,
but it doesn't look like it even has gotten that far yet.
Thanks for any help.
Irv
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org