You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/11/02 21:42:02 UTC
[Proposal] New element to Excalibur Component Manager config (was: Re:
ParentComponentManager & config files)
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.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Proposal] New element to Excalibur Component Manager config (was: Re: ParentComponentManager & config files)
Posted by Peter Donald <do...@apache.org>.
On Sat, 3 Nov 2001 07:42, Berin Loritsch wrote:
> 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.
+1
--
Cheers,
Pete
---------------------------------
I think not; therefore I ain't...
---------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Proposal] New element to Excalibur Component Manager config (was: Re: ParentComponentManager & config files)
Posted by Marcus Crafter <cr...@fztig938.bank.dresdner.net>.
Hi Berin,
> 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"/>
That would be great. :)
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: Managesoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&' Email : Marcus.Crafter@managesoft.com
&&&&. Business Hours : +49 69 9757 200
&&&&&&&:
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Proposal] New element to Excalibur Component Manager config (was:
Re: ParentComponentManager & config files)
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [Proposal] New element to Excalibur Component Manager config (was: Re: ParentComponentManager & config files)
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: den 2 november 2001 21:42
> To: cocoon-dev@xml.apache.org; avalon-dev@jakarta.apache.org
> Subject: [Proposal] New element to Excalibur Component Manager config
> (was: Re: ParentComponentManager & config files)
>
>
> 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!
Sounds fine to me, but how is the path resolved? Should be:
<cm:include-roles href="path/to/new.roles"
resolver="org.apache.avalon.framework.component.WebAppResolver"
contextkey="WEBAPP_CONTEXT"/>
So it can use the contextkey parameter to lookup the webapp context in the
Context map passed to it, and use that to resolve the path and load the
configuration.
/LS
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [Proposal] New element to Excalibur Component Manager config (was: Re: ParentComponentManager & config files)
Posted by Greg Weinger <gw...@itmedicine.net>.
> 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"/>
>
That would be great.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org