View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820633#3820633
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820633 Another thing about the Invocation object in the AOP layer is the concept of metadata resolving. Metadata is resolved from the context of the invocation. This is important because to reuse something like the security interceptor, how it obtains method permissions must be isolated as the definition will be different in JMX, AOP, and EJB land. Furthermore, security is an interesting problem as you don't want to be able to override method permissions from the Invocation's metadata. So we need a method like: resolveConcreteMetaData(group, attribute); So that security can ignore thread and invocation metadata which can be overridden by the user, and instead resolve it from a "secure" place. Bill ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
