cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: XPatch support for maven-cocoon-deployer-plugin
Date Mon, 04 Sep 2006 19:18:29 GMT
Hash: SHA1

On Sun, 3 Sep 2006, Leszek Gawron wrote:

> Date: Sun, 03 Sep 2006 20:00:15 +0200
> From: Leszek Gawron <>
> Reply-To:
> To:
> Subject: Re: XPatch support for maven-cocoon-deployer-plugin
> Reinhard Poetz wrote:
>>  Leszek Gawron (JIRA) wrote:
>> >  I want to implement some more features for cocoon:deploy XPatching:
>>  First, because of a lack of time I haven't had much time to understand in
>>  detail what your needs are. So take my concerns as what they are: a gut
>>  feeling.
>>  I think we are about to overdo what a deployment mechanism (and XPatch) is
>>  about and can/should do for us. Whenver you extend the deployer keep in
>>  mind what Cocoon blocks at a sitemap level are about (polymorphism &
>>  inheritance) and that we can (and IMO should) backport the things that
>>  already work in the OSGi mode. Because of that I don't think it's a good
>>  idea to e.g. be able to patch any file at deployment time instead of only
>>  patching web.xml
> What I really need to patch is web.xml and main sitemap.xmap (which is 
> generated for block testing).
> Probably some entries in WEB-INF/cocoon/xconf are not configurable other way 
> than patching.

I'm not sure what this xpatch stuff is all about (I thought we've been 
over it with patching in 2.2). But what about


if you need special ones for testing your block (packaging=jar)?

For packaging=webapp you don't really need patching at all as you are in 
total control of it!

My -0.02 cents to user driven patching in Cocooon 2.2


- -- 
Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -
Version: GnuPG v1.4.5 (GNU/Linux)


View raw message