-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 3 Sep 2006, Leszek Gawron wrote:
Date: Sun, 03 Sep 2006 20:00:15 +0200
From: Leszek Gawron <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
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
src/test/webapp/WEB-INF/web.xml
src/test/webapp/sitemap.xmap
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
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE/HwHLNdJvZjjVZARArjsAKCvkMJkyHWV3y8e34T1ujoLwZqPaQCfagWJ
M4YrVE5oeahk4kiaIOMJSmo=
=yrB1
-----END PGP SIGNATURE-----
