View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3821352#3821352
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3821352 "starksm" wrote : The invocation of the 'notSetFoo' operation to actually set the 'Foo' attribute still should have type InvocationContext.OP_SETATTRIBUTE. Agreed. "starksm" wrote : However, since an Invocation is already a dispatcher, what I would like to see in the ModelMBeanAttributeInterceptor invoke implementation is: if (setMethod != null) { // if setter was found, invoke the corresponding setter operation try { invocation.dispatch(); } catch (Throwable t) { throw new InvocationException(t); } } With the attribute InvocationContexts setup correctly to have the method dispatcher. Do you see a problem in making this change? Don't see a problem. That was the original intention with Invocation acting as a dispatcher. ------------------------------------------------------- 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
