anonymous wrote : | So why not have an extra parameter where we can limit the contexts, e.g. | One disconnect here is why do we even know the scope should be limited? The only reason that the roles allowed for an invocation should not be overriable at the invocation level is that there is a clear conflict of aspects when a declarative security interceptor is involved. This same scenario can apply to any combination of attributes and interceptors that jboss has no knowledge of, so I view this a more a problem of expressing to the metadata framework what the constraints on a given piece of metadata are. The metadata chain is not just a heirarchical hash map.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861221#3861221 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861221 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
