cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Hunsberger <>
Subject Re: Splitting cocoon.xconf (was Re: Cocoon, a Huge, Scary Beast?)
Date Tue, 21 Dec 2004 14:38:30 GMT
On Tue, 21 Dec 2004 08:51:52 +0100, Sylvain Wallez <> wrote:

<snip>syntax discussion</snip>

> This is a good compromise between automagically loading all *.xconf (see
> my previous answer to Reinhard) and having to explicitely declare all
> imports one by one.
> However, that will work only if Cocoon doesn't run in an unexpanded war
> file. But that should not be a real problem as most deployments are
> using expanded wars, 

Really?  How on earth can you make such a definitive statement?  We
run development expanded much of the time, but production unexpanded,
such a behaviour could catch at least some people by surprise...

> and we can provide some meaningful error messages
> if ever the situation arises.
> So, let's implement the basic <import> first and add little sweeties
> afterwards ;-)

Sounds like a good way to go.

Peter Hunsberger

View raw message