RE: i18nTransformer problems with static pages

Sry for the delay. Shall I commit the StripNameSpaceTransformer to trunk/core/cocoon-pipeline/cocoon-pipeline-components/./transformation , or is there a more preferable location? Should I also add it to the branch? Ard 1) The lightweight StripNameSpaceTransformer ... Add this

Re: i18nTransformer problems with static pages

On 1/3/07, Ard Schrijvers [EMAIL PROTECTED] wrote: Should I also add it to the branch? +1 -Bertrand

Re: Cocoon samples version

On 1/2/07, Jasha Joachimsthal [EMAIL PROTECTED] wrote: ...On the Cocoon samples site at [1] it says the samples are from version 2.1.9... Fixed. The live demo hadn't been updated, I've done it as explained in http://wiki.apache.org/cocoon/CocoonReleaseHowTo. -Bertrand [1]

How do I declare a POJO generator?

bean name=org.apache.cocoon.generation.Generator/partners class=xxx.mobileapi.generation.PartnerGenerator property name=syncDataProvider ref=partnerService/ /bean Is this enough? I probably need to make it protype scope right? -- Leszek GawronCTO at

[jira] Created: (COCOON-1976) [PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement

[PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement - Key: COCOON-1976 URL:

[jira] Updated: (COCOON-1976) [PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement

[ https://issues.apache.org/jira/browse/COCOON-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Berens updated COCOON-1976: --- Attachment: patch.txt [PATCH] NPE in POI ElementProcessorSerializer for characters between

Re: Changes to CForms in 2.1.11-dev

Hi Ralph It depends on what you do in your application and how. If you do lots of custom rendering, have written your own CForms Widgets, stuff like that, then yes, it will probably have an impact. If your application uses the standard rendering pipelines, standard widgets etc. then the

Re: Changes to CForms in trunk

On 3 Jan 2007, at 06:08, Reinhard Poetz wrote: Jeremy Quinn wrote: Hi All As you may have seen from my previous message, I have ripped the bejebus out of CForms over the holidays and just committed the changes. I have the changes all tested and running in BRANCH_2.1.X, but have

Re: Changes to CForms in 2.1.11-dev

Ralph Goers wrote: Jeremy, Does this break binary compatibility? Some of the changes sound like users who upgrade from 2.1.10 to 2.1.11 may have to modify their application? If so, I see that as a problem. While I usually agree with these statements, I think/hope that the benefit of

Re: Object pooling considered harmful

I totally agree that we should avoid object pooling and should in no way introduce this for beans. We have a working pooling implementation for the Avalon components which is transparent (and therefore much better than the original excalibur implementation we use in 2.1.x) and I don't see a need

[continuum] BUILD ERROR: Cocoon Common

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/58/buildId/1478 Build statistics: State: Error Previous State: Error Started at: Wed, 3 Jan 2007 12:11:11 + Finished at: Wed, 3 Jan 2007 12:11:17 + Total

[continuum] BUILD ERROR: Cocoon Configuration Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/61/buildId/1479 Build statistics: State: Error Previous State: Error Started at: Wed, 3 Jan 2007 12:11:22 + Finished at: Wed, 3 Jan 2007 12:11:24 + Total

[continuum] BUILD ERROR: Cocoon Environment [modules]

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/63/buildId/1480 Build statistics: State: Error Previous State: Error Started at: Wed, 3 Jan 2007 12:11:34 + Finished at: Wed, 3 Jan 2007 12:11:36 + Total

[continuum] BUILD ERROR: Cocoon Environment API

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/64/buildId/1481 Build statistics: State: Error Previous State: Error Started at: Wed, 3 Jan 2007 12:11:36 + Finished at: Wed, 3 Jan 2007 12:11:37 + Total

Re: How do I declare a POJO generator?

Leszek Gawron schrieb: bean name=org.apache.cocoon.generation.Generator/partners class=xxx.mobileapi.generation.PartnerGenerator property name=syncDataProvider ref=partnerService/ /bean Is this enough? I probably need to make it protype scope right? Yes, this is enough and yes, scope

Re: Changes to CForms in 2.1.11-dev

Thanks for your support Carsten. On 3 Jan 2007, at 11:43, Carsten Ziegeler wrote: Ralph Goers wrote: Jeremy, Does this break binary compatibility? Some of the changes sound like users who upgrade from 2.1.10 to 2.1.11 may have to modify their application? If so, I see that as a problem.

Re: Trouble w/ trunk / samples

Daniel Fagerstrom wrote: You get the wrong version of DOM, see http://osdir.com/ml/dev@cocoon.apache.org/msg48088.html, for some hints. You can either use JDK 1.5 or put xml-apis, xalan, xerces into your endorsed directory. Carsten -- Carsten Ziegeler - Chief Architect

Re: cocoon-webapp, cocoon-dist-samples (Re: svn commit: r491696 - /cocoon/trunk/core/cocoon-webapp/pom.xml)

Mark Lundquist wrote: I don't get it, why is keeping cocoon-dist-samples working so much harder than making samples work in cocoon-webapp? The dist module requires the latest version of the maven release plugin (I think it is the release plugin, but I might be wrong). So as long as this

Re: cocoon-webapp, cocoon-dist-samples (Re: svn commit: r491696 - /cocoon/trunk/core/cocoon-webapp/pom.xml)

Carsten Ziegeler wrote: Mark Lundquist wrote: I don't get it, why is keeping cocoon-dist-samples working so much harder than making samples work in cocoon-webapp? The dist module requires the latest version of the maven release plugin (I think it is the release plugin, but I might be wrong).

Re: cocoon-webapp, cocoon-dist-samples (Re: svn commit: r491696 - /cocoon/trunk/core/cocoon-webapp/pom.xml)

Reinhard Poetz wrote: Carsten Ziegeler wrote: Mark Lundquist wrote: I don't get it, why is keeping cocoon-dist-samples working so much harder than making samples work in cocoon-webapp? The dist module requires the latest version of the maven release plugin (I think it is the release

Re: What is the deal with blocks

Mark Lundquist skrev: On Jan 2, 2007, at 2:36 PM, Daniel Fagerstrom wrote: Finding some term that doesn't contain the word block for "polymorphic servlet services", would be much less of a problem as it is different from the original block concept and not that many people have used the

Re: Object pooling considered harmful

Joerg Heinicke skrev: On 02.01.2007 23:05, Daniel Fagerstrom wrote: One complication in our work in making the Cocoon components work in a standard Spring container without special Avalon support is that a large amount of our components are Poolable (or more specifically Recyclable). And

Re: i18nTransformer problems with static pages

Ard Schrijvers skrev: Sry for the delay. Shall I commit the StripNameSpaceTransformer to trunk/core/cocoon-pipeline/cocoon-pipeline-components/./transformation , or is there a more preferable location? Should I also add it to the branch? Seem like a reasonable place as long as the

Re: Object pooling considered harmful

Carsten Ziegeler skrev: I totally agree that we should avoid object pooling and should in no way introduce this for beans. We have a working pooling implementation for the Avalon components which is transparent (and therefore much better than the original excalibur implementation we use in

RE: i18nTransformer problems with static pages

Ard Schrijvers skrev: Sry for the delay. Shall I commit the StripNameSpaceTransformer to trunk/core/cocoon-pipeline/cocoon-pipeline-components/./tr ansformation , or is there a more preferable location? Should I also add it to the branch? Seem like a reasonable place as

Re: i18nTransformer problems with static pages

On 1/3/07, Ard Schrijvers [EMAIL PROTECTED] wrote: ...Not sure wether it is common practice to create a jira issue for it when committing something new and resolve it?... I don't think it's common practice here but IMHO it's a Good Thing. -Bertrand

RE: i18nTransformer problems with static pages

On 1/3/07, Ard Schrijvers [EMAIL PROTECTED] wrote: ...Not sure wether it is common practice to create a jira issue for it when committing something new and resolve it?... I don't think it's common practice here but IMHO it's a Good Thing. Locally we added this svn 'pre-commit' hook

Re: What is the deal with blocks

Daniel Fagerstrom schrieb: Another advantage of dropping the prefix block from the polymorphic servlet service stuff is that I get the impression that many people believe that anything that is prefixed with block is incredibly complicated. While the current stuff actually isn't. WDYT?

[jira] Subscription: COCOON-open-with-patch

Issue Subscription Filter: COCOON-open-with-patch (91 issues) Subscriber: cocoon Key Summary COCOON-1976 [PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement https://issues.apache.org/jira/browse/COCOON-1976 COCOON-1974

Re: i18nTransformer problems with static pages

On 03.01.2007 17:47, Ard Schrijvers wrote: Locally we added this svn 'pre-commit' hook to prohibit a commit that did not contain a reference to a jira issue. In jira, via an issue, you can then find the commits that below to it. Although it is sometimes a little annoying, it forces everybody

[continuum] BUILD SUCCESSFUL: Cocoon Blocks Framework Demo Block 1

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/78/buildId/1484 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:49:50 + Finished at: Wed, 3 Jan 2007 19:50:08

[continuum] BUILD SUCCESSFUL: Cocoon Blocks Framework Demo Block 2

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/79/buildId/1485 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:50:38 + Finished at: Wed, 3 Jan 2007 19:50:47

[continuum] BUILD SUCCESSFUL: Cocoon Blocks Framework Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/77/buildId/1486 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:50:50 + Finished at: Wed, 3 Jan 2007 19:51:08

[continuum] BUILD SUCCESSFUL: Cocoon Blocks Framework Sample Blocks

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/80/buildId/1487 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:51:10 + Finished at: Wed, 3 Jan 2007 19:51:22

[continuum] BUILD SUCCESSFUL: Cocoon Pipeline Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/85/buildId/1495 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:53:11 + Finished at: Wed, 3 Jan 2007 19:53:38

[continuum] BUILD FAILURE: Cocoon Sitemap Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/88/buildId/1496 Build statistics: State: Failed Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:53:43 + Finished at: Wed, 3 Jan 2007 19:53:50

[continuum] BUILD SUCCESSFUL: Cocoon Spring Configurator

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/82/buildId/1497 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:53:54 + Finished at: Wed, 3 Jan 2007 19:54:06

[continuum] BUILD SUCCESSFUL: Cocoon Store Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/90/buildId/1498 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:54:09 + Finished at: Wed, 3 Jan 2007 19:54:23

[continuum] BUILD SUCCESSFUL: Cocoon Util

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/93/buildId/1499 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:54:25 + Finished at: Wed, 3 Jan 2007 19:54:35

[continuum] BUILD SUCCESSFUL: Cocoon Webapp

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/94/buildId/1500 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:54:39 + Finished at: Wed, 3 Jan 2007 19:55:06

[continuum] BUILD SUCCESSFUL: Cocoon XML API

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/95/buildId/1501 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:55:12 + Finished at: Wed, 3 Jan 2007 19:55:19

[continuum] BUILD SUCCESSFUL: Cocoon XML Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/96/buildId/1502 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:55:23 + Finished at: Wed, 3 Jan 2007 19:55:35

[continuum] BUILD SUCCESSFUL: Cocoon XML Resolver

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/97/buildId/1503 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 19:55:38 + Finished at: Wed, 3 Jan 2007 19:55:57

[continuum] BUILD SUCCESSFUL: Cocoon Pipeline Components

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/86/buildId/1504 Build statistics: State: Ok Previous State: Failed Started at: Wed, 3 Jan 2007 19:55:59 + Finished at: Wed, 3 Jan 2007 19:56:20 + Total

[continuum] BUILD SUCCESSFUL: Cocoon Thread API

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/91/buildId/1505 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 20:00:52 + Finished at: Wed, 3 Jan 2007 20:01:09

[continuum] BUILD SUCCESSFUL: Cocoon Thread Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/92/buildId/1506 Build statistics: State: Ok Previous Build: No previous build. Started at: Wed, 3 Jan 2007 20:01:14 + Finished at: Wed, 3 Jan 2007 20:01:28

[continuum] BUILD SUCCESSFUL: Cocoon Sitemap Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/88/buildId/1507 Build statistics: State: Ok Previous State: Failed Started at: Wed, 3 Jan 2007 20:03:57 + Finished at: Wed, 3 Jan 2007 20:04:15 + Total

[continuum] BUILD SUCCESSFUL: Cocoon Sitemap Components

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/89/buildId/1508 Build statistics: State: Ok Previous State: Failed Started at: Wed, 3 Jan 2007 20:04:24 + Finished at: Wed, 3 Jan 2007 20:04:40 + Total

[continuum] BUILD FAILURE: Cocoon Core

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/83/buildId/1509 Build statistics: State: Failed Previous State: Failed Started at: Wed, 3 Jan 2007 20:05:22 + Finished at: Wed, 3 Jan 2007 20:05:43 +

[continuum] BUILD SUCCESSFUL: Cocoon Core

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/83/buildId/1510 Build statistics: State: Ok Previous State: Failed Started at: Wed, 3 Jan 2007 20:06:40 + Finished at: Wed, 3 Jan 2007 20:06:52 + Total

Cocoon core test classes don't compile

Is it difficult to fix this? [EMAIL PROTECTED] wrote: Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/83/buildId/1509 Build statistics: State: Failed Previous State: Failed Started at: Wed, 3 Jan 2007 20:05:22

Re: Reducing the number of POM artifacts in trunk

Reinhard Poetz wrote: Carsten Ziegeler wrote: There is one question: In my opinion we have too many parent poms. The configurator is a child of the core-configuration which is a child of core which is a child of Cocoon which is a child of the apache root pom. Is there any way to simplify this?

[jira] Assigned: (COCOON-1976) [PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement

[ https://issues.apache.org/jira/browse/COCOON-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Heinicke reassigned COCOON-1976: - Assignee: Jörg Heinicke [PATCH] NPE in POI ElementProcessorSerializer for characters

[jira] Closed: (COCOON-1976) [PATCH] NPE in POI ElementProcessorSerializer for characters between startDocument and first StartElement

[ https://issues.apache.org/jira/browse/COCOON-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Heinicke closed COCOON-1976. - Resolution: Fixed Fix Version/s: 2.2-dev (Current SVN) 2.1.11-dev

What is the deal with pipelines :-) (was Re: What is the deal with blocks)

On Jan 3, 2007, at 9:29 AM, Alexander Klimetschek wrote: BTW: In sitemaps you have multiple usage of the term pipeline: there is the element pipeline which typically contains multiple matcher with their own pipeline - so you have pipelines there. And inside of act statements you have

Re: Changes to CForms in 2.1.11-dev

On 03 Jan 2007, at 13:21, Jeremy Quinn wrote: But honestly, I worked very hard to minimise the impact !! To put things into perspective: this is the impact of the changes for Daisy: http://svn.cocoondev.org/viewsvn?rev=3594view=rev /Steven -- Steven Noels

Re: Changes to CForms in 2.1.11-dev

Hi Steven I am extremely relieved at how relatively painless that looked !!! Many thanks for sending this. best regards Jeremy On 3 Jan 2007, at 21:57, Steven Noels wrote: On 03 Jan 2007, at 13:21, Jeremy Quinn wrote: But honestly, I worked very hard to minimise the impact !! To put

Re: What is the deal with blocks

On Jan 3, 2007, at 7:16 AM, Daniel Fagerstrom wrote: Mark Lundquist skrev: On Jan 2, 2007, at 2:36 PM, Daniel Fagerstrom wrote: Finding some term that doesn't contain the word block for polymorphic servlet services, would be much less of a problem as it is different from the original

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Grzegorz Kossakowski wrote: Reinhard Poetz napisał(a): I can reproduce this, today. I could swear that it worked when I cut the release two weeks ago also with an empty local repository. Any idea what's going on here? After reading debug log of Maven I can describe what happens partly: In

Re: Managing changes information

Ralph Goers wrote: Carsten Ziegeler wrote: Currently we have a status.xml for each block in trunk already which lists (should list) changes between 2.1.x and 2.2. I think it is far easier to keep track of changes (= add a comment to the changes document) if it sits right next to the code that

Re: Reducing the number of POM artifacts in trunk

Reinhard Poetz wrote: All core modules depend on the core-modules POM now. This means that we only have three layers, for example: trunk/pom.xml pom artifact core/pom.xml ... pom artifact cocoon-xml ... no POM at this

Re: Managing changes information

Reinhard Poetz wrote: Yes. Then I will setup the src/changes/changes.xml files in our modules because I guess that nobody wants to write a StatusReport module for Maven. As I said before this solution comes with the downside that the description doesn't allow mixed content. Instead of having

Re: Managing changes information

Ralph Goers wrote: Reinhard Poetz wrote: Yes. Then I will setup the src/changes/changes.xml files in our modules because I guess that nobody wants to write a StatusReport module for Maven. As I said before this solution comes with the downside that the description doesn't allow mixed content.