Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 28 Aug 2006 17:34:51 +0200
From: Jean-Baptiste Quenot <jbq@apache.org>
To: dev@cocoon.apache.org
Subject: Re: [jira] Created: (COCOON-1898) [PATCH] XPatch support for
 maven-cocoon-deployer-plugin
Message-ID: <20060828153451.GH89053@vision.anyware>
Mail-Followup-To: dev@cocoon.apache.org
References: <2820129.1156402049415.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <2820129.1156402049415.JavaMail.jira@brutus>
User-Agent: mutt-ng/devel-r804 (FreeBSD)

* Lars Trieloff (JIRA):

> The cocoon-deployer-plugin has currently  no support for XPatch,
> which makes it  difficult to modify the  web.xml when developing
> cocoon  blocks. For example  the cocoon-xmldb-impl  block should
> add, when deployed, a servlet  for xindice and a servlet mapping
> for  the xindice  servlet. This was  possible in  2.1 using  the
> XConfToolTask, but is no longer  possible with the current state
> of the deployer-plugin.
>
> My patch adds support for patching the web.xml file using *.xweb
> files in the /conf directory of a block by filtering the block's
> jar file  during deployment  for conf/*.xweb files,  caching the
> patch document  temporarily and  applying them (using  code from
> the orgiginal  XConfToolTask in  2.1) to the  web.xml. The patch
> has currently no support for  other files than conf/*.xweb files
> and does not support any property expansion.

Hey,  that sounds  good.   Has  anyone been  able  to review  this
contribution?
-- 
     Jean-Baptiste Quenot
aka  John Banana Qwerty
http://caraldi.com/jbq/