avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: [Proposal] New element to Excalibur Component Manager config (was: Re: ParentComponentManager & config files)
Date Mon, 05 Nov 2001 13:48:29 GMT


Berin Loritsch a écrit :
> 
> Greg Weinger wrote:
> >
> > > >     I had thought that using cocoon's CM to manage my application's
> > > >     components was the wrong thing to do, because it required
> > > > modifying the
> > > >     cocoon.xconf and cocoon.roles files - part of cocoon and not our
> > > >     application. Was this assumption false ?
> > >
> >
> > I agree, from a maintenance perspective.  You can keep your roles
> > separate in a user.roles file, referenced from the attribute <coocon
> > user-roles="path/to/user.roles"> but there is no standard way I know of
> > to keep your configurations separate, even if you are just "extending"
> > cocoon.
> 
> Hmm.  What if I were to provide an include directive....  Avalon
> Framework now has the notion of Namespaces for configuraiton.  We
> could allow the ComponentManager to look for an element like this:
> 
> <cm:include-roles href="path/to/new.roles"/>
> <cm:include-configuration href="path/to/new.xconf"/>
> 
> If it finds those elements, it will load and use those files as well
> in the system.  That way we can keep our configurations separated
> neatly--even for Cocoon!
> 
> the namespace would be like this:
> 
> xmlns:cm="http://apache.org/avalon/manager/1.0"
> 
> The prefix is not necessary, but this could be useful in many situations.

Don't have a vote here, but it would be +1 :)
-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com

--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message