Sylvain Wallez wrote: > > Thinking further... We could use for the sitemap the <import> > directive I'm currently working on for cocoon.xconf. > > The sitemap components could then be > <map:components> > <map:import src="blah.xconf" roles="blah.roles"/> > ... > </map:components> > After thinking about this a little bit, I agree :)
> Also, do we really need a roles file, which really is a > component writer's concern? The role manager can be setup by > aggregating all cocoon.roles files found in the classpath. > That would make role management totally transparent. Hmm, *I* like this idea, but each time I come up with such a solution everyone shouts "TMM" (too much magic) ;) I think we should support the "roles" attribute; in most cases you don't need it; if you need it you propably would use the resource protocol (loading the roles files from a jar) and in some rare cases (e.g. prototyping) you use a plain file. Carsten
