cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "roy huang" <lingererhu...@hotmail.com>
Subject Re: [woody]display error after upgrade to 2.1.4.It may be a new bug?
Date Thu, 19 Feb 2004 03:46:34 GMT
Sorry, I missed something.
If I use xsltc using <xsl:include href="woody-advanced-field-styling.xsl"/> in woody-samples-styling.xsl
,will occur an error:
org.apache.cocoon.ProcessingException: Unable to get transformer handler for file:/C:/My Documents/IBM/wsad/workspace/PowerOA/WebContent/gtt/common/form/woody-samples-styling.xsl:
org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in creating Transform Handler

cause: org.apache.excalibur.xml.xslt.XSLTProcessorException: Unable to create templates for
stylesheet: file:/C:/My Documents/IBM/wsad/workspace/PowerOA/WebContent/gtt/common/form/woody-samples-styling.xsl

Original Exception: org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in creating
Transform Handler

	at org.apache.excalibur.xml.xslt.XSLTProcessorImpl.getTransformerHandlerAndValidity(XSLTProcessorImpl.java:385)

	at org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:333)

	at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:410)

	at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:652)

	at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:541)

	at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:499)

	at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:155)

	at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)

	at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:165)

	at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:107)

	at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)

	at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:107)

	at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:136)

	at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:371)

	at org.apache.cocoon.components.treeprocessor.TreeProcessor.handleCocoonRedirect(TreeProcessor.java:416)

	at org.apache.cocoon.components.treeprocessor.TreeProcessor.access$000(TreeProcessor.java:101)

	at org.apache.cocoon.components.treeprocessor.TreeProcessor$TreeProcessorRedirector.cocoonRedirect(TreeProcessor.java:577)

	at org.apache.cocoon.environment.ForwardRedirector.redirect(ForwardRedirector.java:93)

	at org.apache.cocoon.components.flow.AbstractInterpreter.forwardTo(AbstractInterpreter.java:275)

	at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.forwardTo(FOM_JavaScriptInterpreter.java:845)

	at org.apache.cocoon.components.flow.javascript.fom.FOM_Cocoon.forwardTo(FOM_Cocoon.java:1534)

	at org.apache.cocoon.components.flow.javascript.fom.FOM_Cocoon.jsFunction_sendPage(FOM_Cocoon.java:306)

	at inv7.invoke()

	at org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:523)

	at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:438)

	at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)

	at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:1105)

	at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)

	at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)

	at org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)

	at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)

	at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.callFunction(FOM_JavaScriptInterpreter.java:719)

	at org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:160)

.......

If I change to use <xsl:include href="woody-field-styling.xsl"/>,everything's fine.

Roy Huang

----- Original Message ----- 
From: "roy huang" <lingererhuang@hotmail.com>
To: <dev@cocoon.apache.org>
Sent: Thursday, February 19, 2004 11:29 AM
Subject: Re: [woody]display error after upgrade to 2.1.4.It may be a new bug?


> Strang result appear after I downgrade to xalan 2.5.1. The xml after woody transform
is like:
> <?xml version="1.0" encoding="utf-8"?>
> <html xmlns="http://www.w3.org/TR/xhtml1/strict">
>  <head>
>   <title>test</title>
>   <link rel="stylesheet" href="../../../common/css/Generic.css"/>
>   <script src="../../../common/js/Generic.js">
>   </script>
>   <script src="./Piwen.js">
>   </script>
>   <meta http-equiv="Pragma" content="no-cache"/>
>  </head>
> ...
> If I use xslt or xalan transform using woody-samples-styling.xsl,the html comes:
> 
> < xmlns="http://www.w3.org/TR/xhtml1/strict">
>  <>
>   <>test</>
>   < rel="stylesheet" href="../../../common/css/Generic.css"/>
>   < src="../../../common/js/Generic.js">
>   </>
>   < src="./Piwen.js">
>   </>
>   
>   < http-equiv="Pragma" content="no-cache"/>
>  </>
> See that?the tag dispear.
> If I change the tranformer to xsltc,every thing back to normal.
> This result won't change if I change  <xsl:include href="woody-advanced-field-styling.xsl"/>
in woody-samples-styling.xsl to  <xsl:include href="woody-field-styling.xsl"/>
> 
> Roy Huang
Mime
View raw message