Sylvain Wallez wrote: > > Can you elaborate on "looks like"? If we load the roles files > from the classpath, this means we define a naming contract > for these files, e.g. > either org/apache/cocoon/cocoon.roles as of today or > META-INF/services/org.apache.cocoon.core.RoleManager. > > So files that "look like" roles file are very likely to be > actual role files and nothing else :-) > Yepp, that's true - hmm, hmm, ahh, what if I just want to drop a particular jar into cocoon as it contains some nice classes. And of course this jar contains such a roles file, but I don't want to get the components added to cocoon; i just want to use the classes. :) Ok, I admit this is very rare - hmm, let me see what other arguments might be against your approach...hmm
Ah, if we scan for all role files contained in the jar, all of these roles are added to the root service manager. But perhaps I want to restrict the access to those components by adding them somewhere down in the hierarchy. This only works by explicitly declaring them, e.g. in the sitemap. Carsten
