Re: help needed for migrating Cocoon2.2 to Spring 3
Hi Robby, I would be *VERY* interested in a new Cocoon 2.3 release with the points you described. Actually I could offer to do some of the work myself or at least have someone in my company paid for committing... What I remember of one of the talks with Reinhard is that the switch to Spring 3 is actually just a problem of the RCL plugin... Most work would probably be to migrate to Dojo 1.x. But if we just change the JS library and make the existing JS code work again, I think we would be fine. Jeremy's proposal with migrating to Dojo 1.x was much deeper: He actually wanted to implement dojo skins and redesign the whole repeater-concept In our case we would be already quite happy with just upgrading to the latest dojo versions. In fact we had to tweak cocoon 2.2 already a lot, that the dojo 0.4.3 stuff works for us, there have been really strange problems... cheers, Gabriel +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien http://www.workflow.at From: Robby Pelssers robby.pelss...@nxp.com To: us...@cocoon.apache.org us...@cocoon.apache.org, dev@cocoon.apache.org dev@cocoon.apache.org Date: 15.09.2011 09:10 Subject:help needed for migrating Cocoon2.2 to Spring 3 Hi all, I’ve seen plenty of people asking for coming up with a new release Cocoon2.3 where cocoon would ship with: - Spring 3 - Dojo 1.x - EhCache 2.3.x - FOP 1.0 In our particular case we would already be satisfied with being able to switch to Spring 3. But so far no single successful upgrade path has been described on the mailinglist. It also looks as no effort is being put in Cocon2.2 anymore. I just want to get some confirmation on this. We might be able to hold of making this switch for a small period of time but as a precaution I want to understand if it is wiser bet my money on Cocoon3 (which does not even have a stable version yet) or wait for a new version of Cocoon2.2 which might never see daylight. Ps. If anyone could already give the steps to take to do it ourselves we would be very thankfull. Kind regards, Robby Pelssers
Re: help needed for migrating Cocoon2.2 to Spring 3
On 09/16/2011 01:18 PM, Gabriel Gruber wrote: What I remember of one of the talks with Reinhard is that the switch to Spring 3 is actually just a problem of the RCL plugin... This problem should be fixed by the latest release of the Cocoon Maven plugin (1.0.0). -- Reinhard Pötz Founder Managing Director, Indoqa and Deepsearch http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org Furthermore, I think Oracle has to honor the JSPA agreement. http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
RE: 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
plugin
groupIdorg.apache.cocoon/groupId
artifactIdcocoon-maven-plugin/artifactId
version1.0.0/version
executions
execution
idprepare/id
phasecompile/phase
goals
goalprepare/goal
/goals
/execution
/executions
/plugin
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)
Re: help needed for migrating Cocoon2.2 to Spring 3
On 16/09/11 14:18, Gabriel Gruber wrote: Most work would probably be to migrate to Dojo 1.x. But if we just change the JS library and make the existing JS code work again, I think we would be fine. Jeremy's proposal with migrating to Dojo 1.x was much deeper: He actually wanted to implement dojo skins and redesign the whole repeater-concept In our case we would be already quite happy with just upgrading to the latest dojo versions. In fact we had to tweak cocoon 2.2 already a lot, that the dojo 0.4.3 stuff works for us, there have been really strange problems... Would it not make more sense to NOT integrate dojo into cocoon 2 (or 3). Dojo is on the client and is designed to receive JSON (or XML) generated by the server. The server should never use Dojo directly (just provide Dojo when the cocoon-based application is loaded in the client). If you keep this separated, it should be very easy to change to another Dojo version. cheers, Gabriel +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien http://www.workflow.at http://www.workflow.at/ From: Robby Pelssers robby.pelss...@nxp.com To: us...@cocoon.apache.org us...@cocoon.apache.org, dev@cocoon.apache.org dev@cocoon.apache.org Date: 15.09.2011 09:10 Subject: help needed for migrating Cocoon2.2 to Spring 3 Hi all, I’ve seen plenty of people asking for coming up with a new release Cocoon2.3 where cocoon would ship with: - Spring 3 - Dojo 1.x - EhCache 2.3.x - FOP 1.0 In our particular case we would already be satisfied with being able to switch to Spring 3. But so far no single successful upgrade path has been described on the mailinglist. It also looks as no effort is being put in Cocon2.2 anymore. I just want to get some confirmation on this. We might be able to hold of making this switch for a small period of time but as a precaution I want to understand if it is wiser bet my money on Cocoon3 (which does not even have a stable version yet) or wait for a new version of Cocoon2.2 which might never see daylight. Ps. If anyone could already give the steps to take to do it ourselves we would be very thankfull. Kind regards, Robby Pelssers -- Andre H. Juffer | Phone: +358-8-553 1161 Biocenter Oulu and | Fax: +358-8-553-1141 Department of Biochemistry | Email: andre.juf...@oulu.fi University of Oulu, Finland | WWW: www.biochem.oulu.fi/Biocomputing/ StrucBioCat | WWW: www.strucbiocat.oulu.fi Triacle Biocomputing | WWW: www.triacle-bc.com
help needed for migrating Cocoon2.2 to Spring 3
Hi all, I've seen plenty of people asking for coming up with a new release Cocoon2.3 where cocoon would ship with: - Spring 3 - Dojo 1.x - EhCache 2.3.x - FOP 1.0 In our particular case we would already be satisfied with being able to switch to Spring 3. But so far no single successful upgrade path has been described on the mailinglist. It also looks as no effort is being put in Cocon2.2 anymore. I just want to get some confirmation on this. We might be able to hold of making this switch for a small period of time but as a precaution I want to understand if it is wiser bet my money on Cocoon3 (which does not even have a stable version yet) or wait for a new version of Cocoon2.2 which might never see daylight. Ps. If anyone could already give the steps to take to do it ourselves we would be very thankfull. Kind regards, Robby Pelssers
