-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Reinhard Poetz wrote: >>> The second one allows "patching" the web.xml by adding snippets from >>> META-INF/cocoon/xpatch to it. It also supports a feature that reverses >>> the classloader hierarchy in a web application by using a shielding >>> classloader. >> >> But can only be used if packaging of the project is war! > > I ported the patching functionality to cocoon:rcl too. In order to be > consistent with our other directory names, the plugins search for patch > files in /COB-INF/cocoon/xpatch/*.xweb. What was the reason to change the path from /META-INF/cocoon/xpatch/*.xweb to /COB-INF/cocoon/xpatch/*.xweb? It's confusing to me to change that. > > But I have to admit that I only tested it very basically because I don't > really use it myself. That's why I'm trying and asking ;-) Ciao and thanks - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (GNU/Linux) iD4DBQFGOFm8LNdJvZjjVZARAiVmAJQLqqVe+SGxOigcyUzRmFze33veAKDtsGR5 4sA6xjYRM6ZIrTzsvLbgOg== =16x4 -----END PGP SIGNATURE-----
