cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: can we move roles.xconf
Date Mon, 07 May 2001 13:21:36 GMT


On Mon, 7 May 2001, Berin Loritsch wrote:

> giacomo wrote:
> >
> > I'd like to suggest to move the roles.xconf file out of the src tree
> > somewhere near to the cocoon.xconf file (BTW I'd like to move
> > cocoon.xconf and roles.xconf file into the WEB-INF directory).
>
> You can move cocoon.xconf anywhere you want.  The major issue is that
> the roles.xconf file should not be accessible outside the jar.  It does
> not contain anything that the average user should alter.  It's existance
> outside the Cocoon jar will generate alot of questions along the lines
> of "what is this roles.xconf file", "what can I change in there", and
> "I changed something and Cocoon doesn't work anymore".  It was separated
> out, because the roles.xconf file is PURELY a developer's concern--so
> it shouldn't be easily accessible.

Ok, I see.

> > On the user list someone asked how to deploy own components without
> > access to the roles.xconf file because it is packed up into the
> > cocoon.jar.
>
> Easy:
>
> <component role="com.mycom.myproj.myrole" class="com.mycom.myproj.myclass"/>
>
> Or if they have something that they need to do selection with:
>
> <component role="com.mycom.myproj.myroleSelector"
>  class="org.apache.avalon.excalibur.DefaultComponentSelector">
>
>   <component-instance name="foo" class="com.mycom.myproj.myclass"/>
>   <component-instance name="bar" class="com.mycom.myproj.myotherclass"/>
> </component>

So these are the ways users define their own components and component
selections in the cocoon.xconf file and users cannot use the abbreviated
syntax, right?

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message