forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bowe, Bastian" <Bastian.B...@astrium.eads.net>
Subject RE: XSP logicsheet: "Component cannot be resolved"
Date Thu, 17 Feb 2005 11:51:24 GMT
I found out that it seems to be a bug of cocoon. I've created a new
bugreport (http://issues.apache.org/bugzilla/show_bug.cgi?id=33616). It
applies to the version shipped with the latest forrest-0.7-dev and to the
cocoon 2.1 trunk. Probably 2.2 is affected too.

> -----Original Message-----
> From: Bowe, Bastian [mailto:Bastian.Bowe@astrium.eads.net] 
> Sent: Tuesday, February 15, 2005 12:58 PM
> To: user@forrest.apache.org
> Subject: XSP logicsheet: "Component cannot be resolved"
> 
> 
> Hello,
> 
> I'm trying to use the SOAP logicsheet in a XSP without 
> success. I'm getting
> 
> // start error (lines 80-80) "Component cannot be resolved or 
> is not a type"
>             manager.release((Component)xscriptManager);
> 
> Anyway the xscript component is specified (not changed by me) 
> in forrest-core.xconf (**/builtin-logicsheet/*@value=xscript)
> 
> This is my xsp:
> <?xml version="1.0" encoding="ISO-8859-1"?>
> 
> <xsp:page
>     language="java"
>     xmlns:xsp="http://apache.org/xsp"
>     xmlns:xsp-request="http://apache.org/xsp/request/2.0"
>     xmlns:xscript="http://apache.org/xsp/xscript/1.0"
>     xmlns:soap="http://apache.org/xsp/soap/3.0">
>   <document> 
>     <header> 
>       <title>My XSP Test</title>
>     </header> 
>     <body> 
>       <section>
>         <title>SOAP Test</title>
>         <p>
>           <soap:call 
> url="http://localhost:9090/SOLICY_SOAP/services/HelloWorld">
>             <ns:hello xmlns:ns="http://soap.solicy.astrium.eads.net"/>
>           </soap:call>
>         </p>
>       </section>
>     </body>
>   </document>
> </xsp:page>
> 
> I've tried successfully my sitemap and the xsp in a cocoon 
> 2.1.6 subapplication.
> 
> I'm using forrest-0.7-dev and have copied jdtcore-2.1.0.jar 
> to $FORREST_HOME/lib/core. XPSs not using xscript or soap 
> logicsheet do work. Other logicsheets, such as session 
> logicsheet work aswell.
> 
> Who does miss something: forrest or me? Any ideas?
> 
> PS: This is an almost complete Stacktrace found in error.log:
> 
> ERROR   (2005-02-15) 12:39.23:053   [access] (/client/status.html)
> PoolThread-4/CocoonServlet: Internal Cocoon Problem
> org.apache.cocoon.ProcessingException: Error executing pipeline.:
> org.apache.cocoon.ProcessingException: Language Exception:
> org.apache.cocoon.components.language.LanguageException: 
> Error compiling
> solicy_xsp:
> ERROR 1 
> (org\apache\cocoon\www\file_\D_\WORK\Bowe\forrest\build\plugin
> s\net_eads_ast
> rium_forrest_plugin_solicy_internal\resources\xsps\solicy_xsp.java):
> ...
>         }
>         public void dispose() {
>           if (xscriptManager != null) {
> // start error (lines 80-80) "Component cannot be resolved or 
> is not a type"
>             manager.release((Component)xscriptManager);
> // end error
>             xscriptManager = null;
>           }
>           super.dispose();
>         }
> ...
> Line 80, column 0: Component cannot be resolved or is not a type
> 	at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeli
> ne.handleExcep
> tion(AbstractProcessingPipeline.java:788)
> 	at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProc
> essingPipeline
> .processXMLPipeline(AbstractCachingProcessingPipeline.java:263)
> ...
> Caused by: org.apache.cocoon.ProcessingException: Language Exception:
> org.apache.cocoon.components.language.LanguageException: 
> Error compiling
> solicy_xsp:
> ERROR 1 
> (org\apache\cocoon\www\file_\D_\WORK\Bowe\forrest\build\plugin
> s\net_eads_ast
> rium_forrest_plugin_solicy_internal\resources\xsps\solicy_xsp.java):
> ...
>         }
>         public void dispose() {
>           if (xscriptManager != null) {
> // start error (lines 80-80) "Component cannot be resolved or 
> is not a type"
>             manager.release((Component)xscriptManager);
> // end error
>             xscriptManager = null;
>           }
>           super.dispose();
>         }
> ...
> Line 80, column 0: Component cannot be resolved or is not a type
> 	at 
> org.apache.cocoon.components.source.impl.SitemapSource.toSAX(S
> itemapSource.j
> ava:359)
> 	at
> org.apache.cocoon.components.source.SourceUtil.parse(SourceUti
> l.java:206)
> 	at
> org.apache.cocoon.sitemap.ContentAggregator.generate(ContentAg
> gregator.java:
> 125)
> 	at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProc
> essingPipeline
> .processXMLPipeline(AbstractCachingProcessingPipeline.java:251)
> 	... 31 more
> org.apache.cocoon.ProcessingException: Language Exception:
> org.apache.cocoon.components.language.LanguageException: 
> Error compiling
> solicy_xsp:
> ERROR 1 
> (org\apache\cocoon\www\file_\D_\WORK\Bowe\forrest\build\plugin
> s\net_eads_ast
> rium_forrest_plugin_solicy_internal\resources\xsps\solicy_xsp.java):
> ...
>         }
>         public void dispose() {
>           if (xscriptManager != null) {
> // start error (lines 80-80) "Component cannot be resolved or 
> is not a type"
>             manager.release((Component)xscriptManager);
> // end error
>             xscriptManager = null;
>           }
>           super.dispose();
>         }
> ...
> Line 80, column 0: Component cannot be resolved or is not a type
> 	at 
> org.apache.cocoon.components.source.impl.SitemapSource.toSAX(S
> itemapSource.j
> ava:359)
> 	at
> org.apache.cocoon.components.source.SourceUtil.parse(SourceUti
> l.java:206)
> 	at
> org.apache.cocoon.sitemap.ContentAggregator.generate(ContentAg
> gregator.java:
> 125)
> ...
> 

Mime
View raw message