On Thu, 2008-08-28 at 06:32 -0400, Tim Williams wrote: > On Thu, Aug 28, 2008 at 5:59 AM, David Crossley <[EMAIL PROTECTED]> wrote: > > Tim Williams wrote: > >> David Crossley wrote: > >> > We intend to "update" the version of Cocoon used by Forrest > >> > to be Cocoon-2.1 branch. > >> > > >> > Please vote. > >> > >> I reckon I've missed discussion on why 2.1.x vs the released 2.2? > >> It's not intuitive why we would "upgrade" to an outdated version. I > >> saw FOR-1016 but I didn't see what the show-stopper was. A search > >> turned up this[1] thread with Thorsten concerned about "pass-through" > >> - but I'm not sure what that means. > > > > That is the ability that lets our sitemaps work. > > If a match is not found then it passes through to the > > next sitemap. That ability was in our old Cocoon-2.2 trunk, > > and we were not sure it was backported to Cocoon-2.1 branch. > > It was and it works for us.
This ability to "look into" different sitemaps is not anymore in 2.2. Meaning our whole concept of mounting a sitemap will not work in 2.2. Which leaves us to rethink and rewrite every single line of our current code. For example the whole plugin infrastructure is based on the "pass-through" mount ability. In cocoon-2.2 if you mount a sitemap you will not come back to the one that issued the mount. Meaning the plugin would need to implement a "re-mount" to the principal sitemap which is highly infinite loop prone. "Updating" - yeah you are right technically we are downgrading our cocoon version - to cocoon-2.1.x let us reuse everything (even the CLI). Still it is a big enhancement to the 3 year old version of cocoon we have now. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
