On 2002.03.07 02:30:21 -0500 Jason Dillon wrote: > > > > > >I think I understand the benefits... I'm not convinced yet that there > are > >no problems we haven't seen yet. I'm still thinking. > > > > The only problem I could see was when a JMX exception was thrown... like > for no such method or whatever... which we would just translate into > some Error. Or could simply ignore, because Dymanic proxy will throw an > error if a undeclared throwable is tossed. It would be better to > decode, but not doing so will result in the came behavior. > > >At the moment I'm thinking that this works best for managed operations > >rather than attributes. I think there may be a reason to keep the > >setAttributes method on the proxy, it we use it: if setting an attribute > >results in cycling through service lifecycle methods, we need to set a > >package of attributes in one cycle. Otherwise the mbean may be > restarted > >in an inconsistent state. Not exactly transaction.... but perhaps > useful. > > > > I would have to check, but I think the MBeanProxy impl in the JBoss/JMX > module will propertly treat set/get calls as attributes and not > operations. > > Otherwise you could have MBeanProxy always return an object that has > generic set/get methods on it... but that seems like a bad idea, since > you will ned to cast to get it and it isn't really that explicit. > Better to just translate under the covers.
To be a little clearer about what I am talking about, I want the "set all these attributes at once" method exposed on the proxy. I haven't looked to see where the method call is distributed into many setAttribute calls, but I assume I'll be able to intercept before that to deal with lifecycle stuff. If we want to use the proxy, note that we will mostly be using xmbeans anyway, so we can generate (using xdoclet) an interface with the managed operations, and setAttributes /getAttributes methods, + whatever individual get/set methods we want. The mbean itself doesn't have to implement the interface. david jencks > > --jason > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
