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: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
