View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3821346#3821346
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3821346 setter chain is the mbean.setAttribute() chain, this however can be mapped to an operation in an MBean -- so you have for instance setAttribute("Foo") mapped to operation "readFoo" rather than the JavaBean setFoo() convention. I redirected the invocation back to the top of the "readFoo" chain in case a) there's a security check that needs to be performed on operation "readFoo" and don't want the setAttribute chain to accidentally bypass this b) there's some semantic in "readFoo" interceptors that should be executed as part of the setAttribute() call. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
