FW: help needed for migrating Cocoon2.2 to Spring 3
Hi Reinhard,
We did read that mail before we posted to the mailinglist.
We have following in our module pom.xml
org.apache.cocoon
cocoon-maven-plugin
1.0.0
prepare
compile
prepare
But when we start the module using the maven jetty plugin we get following
stacktrace:
[INFO] Starting jetty 6.1.26 ...
2011-09-16 13:49:42.696:INFO::jetty-6.1.26
2011-09-16 13:49:42.943:INFO::No Transaction manager found - if your webapp
requires one, please configure one.
log4j:WARN No appenders could be found for logger
(org.apache.commons.jci.monitor.FilesystemAlterationMonitor).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger
(org.apache.commons.jci.stores.MemoryResourceStore).
log4j:WARN Please initialize the log4j system properly.
2011-09-16 13:49:43.410:WARN::Failed startup of context
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@12402e11{/,C:\development\workspaces\nxp\shared\target\rcl\we
bapp}
java.lang.RuntimeException: Cannot load listener
org.apache.cocoon.blockdeployment.BlockDeploymentServletContextListener
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.init(ReloadingListener.java:246)
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.contextInitialized(ReloadingListener.java:148)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:454)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:396)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
at
org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
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:43
Re: Cocoon 2.2/3.0 and Spring WebMVC
Very Nice! So you managed to run cocoon 2.2 with Spring 3.0? Can you provide the community with some hints, or even better supply some patches to a JIRA issue, so it could be picked up by others and could be integrated in the next 2.x version (2.3?) thanx in advance gabriel +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien www.workflow.at From: kremnef To: users@cocoon.apache.org Date: 23.08.2011 13:26 Subject:Re: Cocoon 2.2/3.0 and Spring WebMVC Hi Mark Today I successfully ran cocoon 2.2.1-snapshot and Spring 3.0 I think that some question and problems will be the case. Mark Diggory wrote: > > Cocoon Community, > > While, possibly unconventional, we are considering the the possibility > of marrying Cocoon and WebMVC in our project to use Cocoon as a View > technology while relying on WebMVC as our Controller/Model framework. > I would like to explore if anyone else out there has approached such a > solution? > > Cheers, > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > For additional commands, e-mail: users-h...@cocoon.apache.org > > > -- View this message in context: http://old.nabble.com/Cocoon-2.2-3.0-and-Spring-WebMVC-tp32084435p32318052.html Sent from the Cocoon - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
