cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Supplied defaults from plugin
Date Thu, 13 Jul 2006 13:18:25 GMT
Hash: SHA1

On Thu, 13 Jul 2006, Reinhard Poetz wrote:

> Date: Thu, 13 Jul 2006 13:40:34 +0200
> From: Reinhard Poetz <>
> Reply-To:
> To:
> Subject: Re: Supplied defaults from plugin
> Giacomo Pati wrote:
>>  Hi all
>>  Wouldn't it be cool if the cocoon:deploy goal supplies one with default
>>  files missing in the project src/main/webapp? I can imaging some defaults
>>  for things like, base cocoon.xconf etc. would be
>>  helpfull?
> I moved all default xconf files into the cocoon-core module (you won't find 
> them in cocoon-webapp anymore) so you already get them this way.

I didn't meant those. I've already seen that. But there are still some 
more "defaults".

> about the catalogManager: yes, we could add an option 
> "useDefaultCatalogManager" and add the properties file and the catalogs.

The question might be is it a necessity to have one. If so and there 
isn't one in the deployed webapp the plugin should supply one (without 
the need to configure something).

What I'm thinking of stuff for WEB-INF is:

classes/ as well as entities/
 	dunno whether this is just usefull or needed

 	this is indeed needed but still the plugin can supply a default
 	one. If someone needs to change/add something on it, she/he can
 	copy it to the regular path of the webapp project

 	a default can be supplied here as well IMO.

 	same here, at least in there because it is
 	needed (Cocoon doesn't work without it).


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


View raw message