I am running into the same issue trying to get the JSR 168 portal to work. I installed pluto and the version of tomcat 5.5.x that it uses.
I then loaded the cocoon 2.1.7 jar into it - it expanded nicely, but when I request any cocoon related item, I get the error re. the quartz scheduler. (I deleted the portlet*.jar and the pluto*.jar from the cocoon lib.) Any assistance would be appreciated. thx Paul --- Derek Hohls <[EMAIL PROTECTED]> wrote: > Martin > > Thanks - for now I have reverted to ver 2.1.5.... > but I do think > Cocoon should work "out of the box" with Tomcat on a > Windows > machine - surely that is a common setup?! > > Derek > > (and this page is very much out-of-date: > http://cocoon.apache.org/2.1/installing/ > wrt Tomcat) > > > >>> [EMAIL PROTECTED] 2005/05/20 02:20:03 > PM >>> > I had the same problem. > > can you Read this > > > > > This is only the effect of a previous error. > > Cocoon has the following web.xml configuration: > <load-on-startup>1</load-on-startup> > > This means that Tomcat will load Cocoon at Tomcat > start (as opposed to first > access of CocoonServlet). > > If CocoonServlet throws an exception during init, > Tomcat will consider the > servlet as uninitialized and will try to re-init on > first access. > > Ie one "half-init + break" + another "half-init + > break", which gives you > troubles with anything loaded statically in the JVM > during the part of the > init that actually works (eg configuring the Cron > block and Quartz > scheduler). > > You should search for the previous error in the > Tomcat and/or Cocoon logs > and try to get help on the Cocoon user's list (don't > focus on the > "cannot create a quartz scheduler", during testing > it might also be > easier to set load-on-startup=0 in Cocoon's > web.xml). > > You can use Tomcat's Manager application [1] to > check the init-status > and if Tomcat considers the servlet to be loaded. > > HTH, > Martin > > Derek Hohls ha scritto: > > I am having a problem trying to get Cocoon to run > > under Tomcat and Jetty on a Windows XP machine. > > > > Cocoon : 2.1.7 > > Tomcat: 4.1.31 > > > > Cocoon worked fine when run from the command line > > using Jetty - but when I copied the build > application > > (just using the standard build) over to Tomcat and > > try and start up, I got: > > > > Initialization Problem > > Message: Scheduler with name 'Cocoon' > already exists. > > Description: > org.apache.avalon.framework.configuration.ConfigurationException: > cannot create a quartz scheduler > > Sender: org.apache.cocoon.servlet.CocoonServlet > > Source: Cocoon Servlet > > cause > > org.quartz.SchedulerException: Scheduler with name > 'Cocoon' already exists. > > request-uri > > /cocoon/ > > > > I then altered the local.build.properties file to > comment > > out the "cron" block - as per the suggestion in > the thread: > > > http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=110539967327519&w=2 > > > > > The problem now is that Cocoon does not run under > Jetty OR Tomcat: > > > > > > In Jetty: > > > > Initialization Problem > > Message: Could not find component (key > [org.apache.cocoon.components.cron.JobScheduler]) > > Description: > org.apache.avalon.framework.configuration.ConfigurationException: > Could not load class > org.apache.cocoon.portal.coplets.basket.AddToBasketAspect > for component named 'basket' at > file:/D:/cocoon-2.1.7/build/webapp/WEB-INF/cocoon.xconf:1800:94 > > Sender: org.apache.cocoon.servlet.CocoonServlet > > Source: Cocoon Servlet > > > > cause > > > org.apache.avalon.framework.component.ComponentException: > Could not find component (key > [org.apache.cocoon.components.cron.JobScheduler]) > > > > request-uri > > / > > > > > > Also, under Tomcat: > > > > HTTP Status 500 - > > type Exception report > > > > message > > description The server encountered an internal > error () that prevented it from fulfilling this > request. > > > > exception > > javax.servlet.ServletException: Servlet.init() for > servlet Cocoon threw exception > > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:916) > > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:621) > > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:163) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) > > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) > > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) > > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) > > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358) > > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) > > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594) > > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594) > > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) > > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127) > > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) > > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) > > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) > > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152) > > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) > > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) > > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) > > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) > > at java.lang.Thread.run(Unknown Source) > > > > > > root cause > > > > java.lang.NoSuchMethodError: > org.apache.xerces.xni.grammars.XSGrammar.toXSModel()Lorg/apache/xerces/xs/XSModel; > === message truncated === This communication, including attachments, is for the exclusive use of the addressee and may contain proprietary, confidential, or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination, or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender by return mail and delete this communication and destroy all copies. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
