You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Felix Knecht <fe...@otego.com> on 2007/02/13 15:19:27 UTC

Running from released trunk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've an application running on c2.2. Before the RC1 everything worked
well. With RC1 I can build the applications war file like before (I'm
happy to see the RC1 finally ;-) ). But running the application by mvn
jetty:run it can't find schema reference for the sitemap (see below).
Can somebody point me to the right direction?

Thanks
Felix

2007-02-13 15:07:53.840::WARN:  Nested in
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'com.unilever.research.yellowpages.servlet':
Invocation of init method failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not
create TreeProcessor; nested exception is java.lang.RuntimeException:
Unable to parse sitemap schema.:
java.lang.RuntimeException: Unable to parse sitemap schema.
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.<init>(TreeProcessor.java:125)
        at
org.apache.cocoon.sitemap.SitemapServlet$RequestProcessor.getProcessor(SitemapServlet.java:91)
        at
org.apache.cocoon.servlet.RequestProcessor.<init>(RequestProcessor.java:99)
        at
org.apache.cocoon.sitemap.SitemapServlet$RequestProcessor.<init>(SitemapServlet.java:71)
        at
org.apache.cocoon.sitemap.SitemapServlet.init(SitemapServlet.java:52)
        at javax.servlet.GenericServlet.init(GenericServlet.java:211)
        at
org.apache.cocoon.servletservice.spring.ServletFactoryBean.init(ServletFactoryBean.java:117)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1160)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1122)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1085)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:429)
        at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:250)
        at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:141)
        at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:247)
        at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:161)
        at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:270)
        at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
        at
org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
        at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
        at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
        at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
        at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:451)
        at
org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
        at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1219)
        at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:421)
        at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:496)
        at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
        at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
        at org.mortbay.jetty.Server.doStart(Server.java:228)
        at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at
org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
        at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:332)
        at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:277)
        at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:195)
        at
org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.xml.sax.SAXParseException: schema_reference.4: Failed
to read schema document 'null', because 1) could not find the
document; 2) the document could not be read; 3) the root element of
the document is not <xsd:schema>.
        at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
        at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172)
        at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
        at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:2245)
        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchema(XSDHandler.java:1590)
        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:438)
        at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:556)
        at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:523)
        at
com.sun.org.apache.xerces.internal.jaxp.validation.xs.SchemaFactoryImpl.newSchema(SchemaFactoryImpl.java:206)
        at
javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:489)
        at
org.apache.cocoon.components.treeprocessor.TreeProcessor.<init>(TreeProcessor.java:123)
        ... 61 more

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF0cju2lZVCB08qHERAu5dAKCz7ZCz1ppLaHD0dB26ebjy5f4W1gCgveuC
PBczhljFOIfwwrg17PO9CZU=
=Y/Jz
-----END PGP SIGNATURE-----


Re: Running from released trunk

Posted by Felix Knecht <fe...@otego.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vadim Gritsenko schrieb:
> Carsten Ziegeler wrote:
>> Felix Knecht schrieb:
>>> I've an application running on c2.2. Before the RC1 everything
>>> worked well. With RC1 I can build the applications war file
>>> like before (I'm happy to see the RC1 finally ;-) ). But
>>> running the application by mvn jetty:run it can't find schema
>>> reference for the sitemap (see below). Can somebody point me to
>>> the right direction?
>>>
>> Argh, unnoticed my anyone (including myself), Eclipse went mad
>> again and instead of updating the sitemap schema, it removed the
>> sitemap schema from svn in this commit
>> http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=117120391223417&w=2
>>
>
> BTW, what is our official position on mark of the devil? Do we
> tolerate it?
>
> +<?xml version="1.0" encoding="UTF-8"?>

But thank god it seems to work ...
Felix

>
>
> Vadim
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF0dIV2lZVCB08qHERAoQ4AJwMvBIBTXq3U6AG8DoxHjIMti+zAQCg6p23
cAON1COdtxV1IjHaLmJ2fIs=
=g2L+
-----END PGP SIGNATURE-----


Re: Running from released trunk

Posted by Carsten Ziegeler <cz...@apache.org>.
Vadim Gritsenko wrote:
>> Can you remove it?
> 
> Done.
> 
Thanks, it's not visible in my ide :(
(Given the recent problems I should perhaps switch back to a more stable
version...)

Carsten

-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Re: Running from released trunk

Posted by Vadim Gritsenko <va...@reverycodes.com>.
Carsten Ziegeler wrote:
> Vadim Gritsenko wrote:
> 
>> BTW, what is our official position on mark of the devil? Do we tolerate it?
>>
>>    +<?xml version="1.0" encoding="UTF-8"?>
>>
> No, where do you see it?

http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=117137702328252
http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-sitemap/cocoon-sitemap-impl/src/main/resources/org/apache/cocoon/sitemap/schema/cocoon-sitemap-1.0.xsd?view=markup&pathrev=507020

> Can you remove it?

Done.

Vadim

Re: Running from released trunk

Posted by Carsten Ziegeler <cz...@apache.org>.
Vadim Gritsenko wrote:

> 
> BTW, what is our official position on mark of the devil? Do we tolerate it?
> 
>    +<?xml version="1.0" encoding="UTF-8"?>
> 
No, where do you see it? Can you remove it?

Carsten


-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Re: Running from released trunk

Posted by Vadim Gritsenko <va...@reverycodes.com>.
Carsten Ziegeler wrote:
> Felix Knecht schrieb:
>> I've an application running on c2.2. Before the RC1 everything worked
>> well. With RC1 I can build the applications war file like before (I'm
>> happy to see the RC1 finally ;-) ). But running the application by mvn
>> jetty:run it can't find schema reference for the sitemap (see below).
>> Can somebody point me to the right direction?
>>
> Argh, unnoticed my anyone (including myself), Eclipse went mad again and
> instead of updating the sitemap schema, it removed the sitemap schema
> from svn in this commit
> http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=117120391223417&w=2

BTW, what is our official position on mark of the devil? Do we tolerate it?

   +<?xml version="1.0" encoding="UTF-8"?>


Vadim

Re: Running from released trunk

Posted by Carsten Ziegeler <cz...@apache.org>.
Felix Knecht schrieb:
> I've an application running on c2.2. Before the RC1 everything worked
> well. With RC1 I can build the applications war file like before (I'm
> happy to see the RC1 finally ;-) ). But running the application by mvn
> jetty:run it can't find schema reference for the sitemap (see below).
> Can somebody point me to the right direction?
> 
Argh, unnoticed my anyone (including myself), Eclipse went mad again and
instead of updating the sitemap schema, it removed the sitemap schema
from svn in this commit
http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=117120391223417&w=2

I readed the sitemap so it should work now again.

Carsten
-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Re: Running from released trunk

Posted by Felix Knecht <fe...@otego.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Carsten. Your latest commit make it working again.

Regards
Felix
> I've an application running on c2.2. Before the RC1 everything
> worked well. With RC1 I can build the applications war file like
> before (I'm happy to see the RC1 finally ;-) ). But running the
> application by mvn jetty:run it can't find schema reference for the
> sitemap (see below). Can somebody point me to the right direction?
>
> Thanks Felix
>
> 2007-02-13 15:07:53.840::WARN:  Nested in
> org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name
> 'com.unilever.research.yellowpages.servlet': Invocation of init
> method failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not
> create TreeProcessor; nested exception is
> java.lang.RuntimeException: Unable to parse sitemap schema.:
> java.lang.RuntimeException: Unable to parse sitemap schema.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF0c0m2lZVCB08qHERAjGfAJ95TYYrcj5eoLS8KSVQ6uH3pbt5pgCgq6A5
9tb8DaqTuS8A/sjYtKQYaxQ=
=Jgc1
-----END PGP SIGNATURE-----