You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2005/05/19 04:54:55 UTC
Chaperon jar is required by core (Was: svn commit: r170628)
The chaperon jar is required by the core, so i have moved it back.
Please, please move one jar and test, next jar, test.
Can anyone see why Chaperon is required in the core?
Here is output from doing 'forrest run' without Chaperon.
Doing 'forrest' is okay no errors.
------------------------------
12:49:39.622 WARN!! Error for /index.html
java.lang.NoClassDefFoundError: net/sourceforge/chaperon/process/LexicalProcessor
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:207)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:171)
at org.apache.cocoon.core.container.ComponentEnvironment.loadClass(ComponentEnvironment.java:59)
at org.apache.cocoon.core.container.AbstractComponentHandler.getComponentHandler(AbstractComponentHandler.java:73)
at org.apache.cocoon.core.container.CoreServiceManager.getComponentHandler(CoreServiceManager.java:585)
at org.apache.cocoon.core.container.CoreServiceManager.addComponent(CoreServiceManager.java:474)
at org.apache.cocoon.components.container.CocoonServiceManager.addComponent(CocoonServiceManager.java:58)
at org.apache.cocoon.core.container.DefaultServiceSelector.configure(DefaultServiceSelector.java:121)
at org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector.configure(ComponentsSelector.java:121)
at org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:240)
at org.apache.cocoon.core.container.DefaultServiceSelector$Factory.setupInstance(DefaultServiceSelector.java:212)
at org.apache.cocoon.core.container.ComponentFactory.newInstance(ComponentFactory.java:109)
at org.apache.cocoon.core.container.ThreadSafeComponentHandler.doInitialize(ThreadSafeComponentHandler.java:52)
at org.apache.cocoon.core.container.AbstractComponentHandler.initialize(AbstractComponentHandler.java:265)
at org.apache.cocoon.core.container.AbstractComponentHandler.getComponentHandler(AbstractComponentHandler.java:121)
at org.apache.cocoon.core.container.CoreServiceManager.getComponentHandler(CoreServiceManager.java:585)
at org.apache.cocoon.core.container.CoreServiceManager.addComponent(CoreServiceManager.java:474)
at org.apache.cocoon.components.container.CocoonServiceManager.addComponent(CocoonServiceManager.java:58)
at org.apache.cocoon.core.container.CoreServiceManager.parseConfiguration(CoreServiceManager.java:637)
at org.apache.cocoon.core.container.CoreServiceManager.configure(CoreServiceManager.java:175)
at org.apache.cocoon.components.treeprocessor.sitemap.SitemapLanguage.createServiceManager(SitemapLanguage.java:80)
at org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:328)
at org.apache.cocoon.components.treeprocessor.TreeProcessor.buildConcreteProcessor(TreeProcessor.java:401)
at org.apache.cocoon.components.treeprocessor.TreeProcessor.setupConcreteProcessor(TreeProcessor.java:348)
at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247)
at org.apache.cocoon.Cocoon.process(Cocoon.java:503)
at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1097)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501)
------------------------------
> Author: cheche
> Date: Tue May 17 10:59:08 2005
> New Revision: 170628
>
> URL: http://svn.apache.org/viewcvs?rev=170628&view=rev
> Log:
> move chaperon out of core to plugin.input.wiki
>
> Added:
> forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/lib/
> forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/lib/chaperon-20040205.jar
> - copied unchanged from r170615, forrest/trunk/lib/core/chaperon-20040205.jar
> Removed:
> forrest/trunk/lib/core/chaperon-20040205.jar
Re: Chaperon jar is required by core (Was: svn commit: r170628)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> The chaperon jar is required by the core, so i have moved it back.
> Please, please move one jar and test, next jar, test.
>
> Can anyone see why Chaperon is required in the core?
In the main sitemap.xmap I had moved [1] the chaperon parser because of
a Cocoon 2.2 error.
In there you can read:
"
<!--
FIXME: there is a bug in the Cocoon 2.2 resolving that can make
cocoon:/ calls call the base sitemap; remove the
following when it's fixed.
-->
"
[1] version 37459, Fri Sep 3 06:36:26 2004 UTC
http://svn.apache.org/viewcvs.cgi/forrest/trunk/src/core/context/sitemap.xmap?rev=37459&r1=37393&r2=37459&diff_format=h
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Chaperon jar is required by core (Was: svn commit: r170628)
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> David Crossley wrote:
> > The chaperon jar is required by the core, so i have moved it back.
> > Please, please move one jar and test, next jar, test.
> >
> > Can anyone see why Chaperon is required in the core?
> > Here is output from doing 'forrest run' without Chaperon.
> > Doing 'forrest' is okay no errors.
>
> That is because there is a match on sitemap for dynamic creation of gramars:
> <map:match pattern="*.xlex">
>
> I have a patch, but I am not 100% sure how that will affect input.wiki
> plugin.
>
> WDYT?
I think leave Chaperon in the core, record a Jira issue,
add your patch and Nicola Ken's notes, and leave it until later.
I was just fixing the broken build so that we can get going
with other things.
One issue that i did wonder about at this stage, is why
the error appeared with 'forrest run' but not 'forrest site'.
--David
Re: Chaperon jar is required by core (Was: svn commit: r170628)
Posted by Juan Jose Pablos <ch...@apache.org>.
David Crossley wrote:
> The chaperon jar is required by the core, so i have moved it back.
> Please, please move one jar and test, next jar, test.
>
> Can anyone see why Chaperon is required in the core?
> Here is output from doing 'forrest run' without Chaperon.
> Doing 'forrest' is okay no errors.
>
That is because there is a match on sitemap for dynamic creation of gramars:
<map:match pattern="*.xlex">
I have a patch, but I am not 100% sure how that will affect input.wiki
plugin.
WDYT?
Cheche