Sylvain Wallez wrote: > > Honestly, I consider the requirement to explicitely declare > the roles files that are present in jar files "TMC" (too much > complexity) ;-) or more precisely it requires users to know > things about the Cocoon internals that they shouldn't really > have to care about (and that they don't care about today). > :) Now, I don't call this TMM, either - it just seems that everytime *I* propose these things, everyone else calls it TMM :(
Anyways, I see a potential problem with this: as soon as you drop a jar file into Cocoon with a file that *looks like* a cocoon roles file, this is tried to be used which might result in errors etc. So I think in this case, explicitly using role files is easier. It is correct that currrently users don't care about the roles file and in fact we don't really need it. Today we have many components in the cocoon.xconf where their role is not defined in the roles file. On the other hand, I tend to agree with you, that you would rarely need to use a roles file on a per sitemap base. I currently see use cases for this like the portal where you get a complete template application, including a template sitemap etc. And the portal uses it's own roles file, so the template sitemap already contains a reference to the roles file contained in the portals.jar. Carsten
