anonymous wrote : | So why not have an extra parameter where we can limit the contexts, e.g. |
Actually, thinking about this some more, it does make some sense in the context of the security interceptor trying to enforce declarative security based on the deployment roles. The security interceptor does know as part of its behavior that it only cares about the roles from the deployment scope. There still is the question of whether there should be controll over what scopes should allow for the introduction of a given piece of metadata. This is actually an intersection of security with metadata, so perhaps it could be punted to a security aspect on the metadata service. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861226#3861226 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861226 ------------------------------------------------------- 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
