You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Marcus Crafter <cr...@fztig938.bank.dresdner.net> on 2002/02/07 20:34:47 UTC
Application level config file/s ?
Hi All,
Hope all is well.
I've been thinking recently about whether or not it makes sense
to be able to separate the cocoon.xconf configuration file, so
that application developers who choose to use Avalon, if they
wish, can have their component's configuration details separate to
those of Cocoon.
Cocoon currently has the notion of user-roles to allow just this
for role definitions, and to me it seems like a good idea to
allow this at the component configuration level too ? perhaps even to
the extent of being able to nest configuration files in a hierarchical
fashion much like how we have nested sitemaps.
What do you all think about supporting something like a user-config
declaration, or some similar concept of nested/included config files ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Application level config file/s ?
Posted by Peter Royal <pr...@managingpartners.com>.
On Thursday 07 February 2002 02:34 pm, Marcus Crafter wrote:
> Cocoon currently has the notion of user-roles to allow just this
> for role definitions, and to me it seems like a good idea to
> allow this at the component configuration level too ? perhaps even to
> the extent of being able to nest configuration files in a hierarchical
> fashion much like how we have nested sitemaps.
>
> What do you all think about supporting something like a user-config
> declaration, or some similar concept of nested/included config files ?
something along these lines was recently discussed on the avalon lists, and
one answer was to just use XML entities!
see
http://www.mail-archive.com/avalon-phoenix-dev%40jakarta.apache.org/msg00041.html
-pete
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org