Re: Caching jx *without* flow
Thorsten Scherler wrote: Hi all, hi Ard, http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=115194685214066w=2 ... Now, the cached jx would depend on these three parameters. Very easy to use, and less error prone than the flow part. If somebody is interested in the code I will hear Yes very interested. http://svn.apache.org/viewvc?view=revrev=446701 https://issues.apache.org/jira/browse/FOR-931 Can you attach a patch to this issue or commit it to cocoon directly? Would be awesome. Do I get it right: you want to patch JXTG to automatically build up a cache key from cocoon parameters? map:match pattern=foo map:generate src=foobar.jx map:parameter name=foo value=bar/ map:parameter name=bar value=foo/ /map:generate map:serialize/ /map:match so cocoon:/foo gets cached with something like foo=barbar=foo? Why need a patch for that? After all you already have jx:cache-key and jx:cache-validity. -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
Rice Yeh wrote: Hi, At each hot deployment on jetty, I always get the following exception and then the whole jetty is not working anymore. Any clue? Regards, Rice 4583451 [Thread-5] INFO / - Error during initializing Apache Cocoon 2.2.0-M1 - a did you try trunk version? LOTS have changed. BTW: how do you hot deploy to jetty? -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [M10N] Eclipse projects
Joerg Heinicke wrote: Hi, I tried the Maven build at home and it worked. Only eclipse:eclipse generates some project definitions, which don't work: cocoon-template-impl had a wrong source dir, so that package declaration did not match the package set in Eclipse. Same is true for cocoon-22-archetype-block. cocoon-blocks-fw-tests seems to miss many dependencies at least for src/test/java. Is this something we can influence at all? Is this a problem of the Maven Eclipse plugin? Or is everything left to the project wizard of Eclipse? Jörg Are you refering to maven eclipse plugin which you invoke by mvn eclipse:eclipse or to m2eclipse (which is an eclipse plugin for handling maven projects)? I've been testing both and both have significant bugs but I did manage to get m2eclipse usable. The biggest m2eclipse problems are: - not being able to switch to offline (even though this is configurable) - sometimes transitive dependencies have to be stated explicitly: - they are either not included in .classpath - or the opposite: you get two same artifacts on classpath only with different versions - I've run into some infinite loops (eclipse hung consuming all resources) when having a project subclipsed and then maven enabled. -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Explanation of the Cocoon directory structure
Dev at weitling wrote: Hi! The Cocoon directory structure isn't very concise: many directories with the same or at least similar names at different locations, some directories with non-intuitive names (e.g. lib/endorsed: why endorsed?). If there's a problem I don't know where to look, I don't know where to place my files, I don't know which parts are superfluous and and and... Are docs about that anywhere in the outside world without having to pay $ 30 for an outdated book? which cocoon version are you refering to ? -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [M10N] Eclipse projects
On 17.09.2006 14:38, Leszek Gawron wrote: Is this something we can influence at all? Is this a problem of the Maven Eclipse plugin? Or is everything left to the project wizard of Eclipse? Are you refering to maven eclipse plugin which you invoke by mvn eclipse:eclipse or to m2eclipse (which is an eclipse plugin for handling maven projects)? One is the Maven Eclipse plugin, the other one the Eclipse Maven plugin ;) I refer to Maven plugin invoked via eclipse:eclipse as described in our readme.txt or in Daisy. Jörg
Re: Explanation of the Cocoon directory structure
Hi Florian, On 13.09.2006 23:27, Dev at weitling wrote: The Cocoon directory structure isn't very concise: many directories with the same or at least similar names at different locations, some directories with non-intuitive names (e.g. lib/endorsed: why endorsed?). I can't agree. Cocoon 2.1, which you are probably using, has a quite simple directory structure. Not everything might be obvious on the first sight, but you might ask more specific questions to get it explained. The endorsed dir you refer to is nothing Cocoon specific, but a general Java 1.4 problem with XML libs: http://wiki.apache.org/cocoon/EndorsedLibsProblem. If there's a problem I don't know where to look, I don't know where to place my files, I don't know which parts are superfluous and and and... There is some documentation available to get started. Furthermore you can have a look into the block structure and adapt one, especially the tour block, which introduces the most important ones: http://cocoon.zones.apache.org/demos/release/samples/blocks/tour/intro/docs/index.html (also available in your local installation). Later one you should not integrate your code into Cocoon's build, but integrate Cocoon into your build. Jörg
Re: [WEBSITE] 2.1/installing/jars.html
On 13.09.2006 23:55, Dev at weitling wrote: And: On the left side there's the point Updating to version 2.1.5. May it be outdated or was that a difficult change? Yes, migrating to 2.1.5 had some implications as you can read on the first two topics. But the rest of the document is more a Updating from 2.0.x to 2.1.x. So the document might be wrongly named. In general the migration at the patch level (x.y.z-1 to x.y.z) should be quite smooth. Mostly it's sufficient to exchange the Jars. Jörg
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
Rice Yeh wrote: I tried the 2.2.0-M2-SNAPSHOT (the trunk), but I get the following error message. It seems that CocoonServletListener does not exist any more. But cocoon:deploy still have web.xml using the listener. You have not used the latest cocoon:deploy version. [INFO] Started configuring web.xml, resource base=C:\projects\XS\school\xs-schoo l-cocoon\target\xs-school-cocoon 501 [main] WARN org.mortbay.log - Could not instantiate listener org.apache.coco on.servlet.CocoonServletListener java.lang.ClassNotFoundException : org.apache.cocoon.servlet.CocoonServletListene r at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass (URLClassLoader.java:188) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:334) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:305) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.jav a:784) For hot deployment, it is jetty6:run 's function. It will scan webapp's change if I have the following configuration in the pom.xml (I have scanIntervalSeconds set to 10 seconds). I see .. the maven plugin. I thought you had a separate jetty instance. -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
Do you know how to use the cocoon:deploy on a specifice version? In my local repository, I have 1.0.0-M1, 1.0.0-M2-SNAPSHOT, 1.0.0-SNAPSHOT.On 9/17/06, Leszek Gawron [EMAIL PROTECTED] wrote: Rice Yeh wrote: I tried the 2.2.0-M2-SNAPSHOT (the trunk), but I get the following error message. It seems that CocoonServletListener does not exist any more. But cocoon:deploy still have web.xml using the listener. You have not used the latest cocoon:deploy version. [INFO] Started configuring web.xml, resource base=C:\projects\XS\school\xs-schoo l-cocoon\target\xs-school-cocoon 501 [main] WARN org.mortbay.log - Could not instantiate listener org.apache.coco on.servlet.CocoonServletListener java.lang.ClassNotFoundException : org.apache.cocoon.servlet.CocoonServletListene r at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass (URLClassLoader.java :188) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:334) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:305) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.jav a:784) For hot deployment, it is jetty6:run 's function. It will scan webapp's change if I have the following configuration in the pom.xml (I have scanIntervalSeconds set to 10 seconds).I see .. the maven plugin. I thought you had a separate jetty instance.--Leszek Gawron, IT ManagerMobileBox sp. z o.o.+48 (61) 855 06 67http://www.mobilebox.plmobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
Oh! I just find the answer. it is still in the pom.xml.On 9/18/06, Rice Yeh [EMAIL PROTECTED] wrote: Do you know how to use the cocoon:deploy on a specifice version? In my local repository, I have 1.0.0-M1, 1.0.0-M2-SNAPSHOT, 1.0.0-SNAPSHOT.On 9/17/06, Leszek Gawron [EMAIL PROTECTED] wrote: Rice Yeh wrote: I tried the 2.2.0-M2-SNAPSHOT (the trunk), but I get the following error message. It seems that CocoonServletListener does not exist any more. But cocoon:deploy still have web.xml using the listener. You have not used the latest cocoon:deploy version. [INFO] Started configuring web.xml, resource base=C:\projects\XS\school\xs-schoo l-cocoon\target\xs-school-cocoon 501 [main] WARN org.mortbay.log - Could not instantiate listener org.apache.coco on.servlet.CocoonServletListener java.lang.ClassNotFoundException : org.apache.cocoon.servlet.CocoonServletListene r at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass (URLClassLoader.java :188) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:334) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoade r.java:305) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.jav a:784) For hot deployment, it is jetty6:run 's function. It will scan webapp's change if I have the following configuration in the pom.xml (I have scanIntervalSeconds set to 10 seconds).I see .. the maven plugin. I thought you had a separate jetty instance.--Leszek Gawron, IT ManagerMobileBox sp. z o.o.+48 (61) 855 06 67http://www.mobilebox.plmobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
[cforms] cleanupHook NOT called when exception occurs
Hi, I try to use the cleanupHook in a form to clean up resource allocated during restoreHook or other places . I find that cform does not call cleanupHook if some exception happens before it. Reading the Form.js, I find cleanupHook is NOT wrapped in a finally statement. Is this a bug? Or there is other way to guarantee cleanupHook invocation. Regards,Rice
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
I tried the trunk version and it seems it is not stable yet because I get the following error:1903 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0: 1903 [main] WARN org.mortbay.log - failed [EMAIL PROTECTED][INFO] Jetty server exiting.[INFO] [ERROR] BUILD ERROR[INFO] [INFO] FailureEmbedded error: Cannot invoke listener org.springframework.web.context.ContextLo[EMAIL PROTECTED]Class [org.apache.cocoon.core.container.spring.CocoonNamespaceHandler] does notimplement the NamespaceHandler interface [INFO] [INFO] Traceorg.apache.maven.lifecycle.LifecycleExecutionException: Failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:559) 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.executeTaskSegmen ts(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.apache.maven.plugin.MojoExecutionException: Failure at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty (AbstractJettyMojo.java:296) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:242) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java :122) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:160) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:534) ... 16 moreCaused by: java.lang.RuntimeException: Cannot invoke listener org.springframewor[EMAIL PROTECTED] at org.apache.cocoon.bootstrap.servlet.ShieldingListener.invoke (ShieldingListener.java:180) at org.apache.cocoon.bootstrap.servlet.ShieldingListener.contextInitialized(ShieldingListener.java:203) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler. java:368) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:957) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:341) at org.mortbay.jetty.webapp.WebAppContext.doStart (WebAppContext.java:367) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:37) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:101) at org.mortbay.jetty.Server.doStart(Server.java:235) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:37) at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer. java:114) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:285) ... 21 moreCaused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unexp ected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.apache.cocoon.core.container.spring.CocoonNamespaceHandler ] does not implement the NamespaceHandler interface at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:403) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea nDefinitions(XmlBeanDefinitionReader.java:340) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:315) at org.springframework.beans.factory.support.AbstractBeanDefinitionReade r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:142) at
Re: Unable to initialize Avalon component with role org.apache.cocoon.caching.Cache
Rice Yeh wrote: Do you know how to use the cocoon:deploy on a specifice version? In my local repository, I have 1.0.0-M1, 1.0.0-M2-SNAPSHOT, 1.0.0-SNAPSHOT. checkout trunk version via svn and build it. Use a proper version in a pom.xml file. You have all the necessary steps outlined at http://ouzo.squash.eu.org/2006/09/creating_a_mavenized_cocoon_ap.html Current cocoon:deploy version is 1.0.0-M2-SNAPSHOT (please mind that actual content differs basing on when you last built the plugin). -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
map:components cannot be in sitemap.xml anymore?
Hi, I tried the myBlock example with the latest trunk. jetty gets up successfully and I use browser to connect it. The following error message is shown on browser. Does it mean that map:components cannot be in sitemap.xml anymore? I have map:components removed, then it goes well.Unexpected element components at file:/C:/tmp/cocoon/yourBlock/target/yourBlock/sitemap.xmap:17:19Rice