Problem one if focusing on JMX over JBoss-JMX. The order is JBoss-JMX and then JMX generically. Twiddling attributes is an operation indepedent of restarting a service and if you don't agree with that then we are at a viewpoint impass. Setting a RW attribute has an effect. Its just not the effect you are looking for so either get on board and work within the service life cycle or go play in your JMX sandbox.
Scream and shout about the purity of RW JMX attributes all you want, I don't buy it. Services with exposure of their attribute via JMX with their attendent life cycle management comes first. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Matt Munz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 24, 2003 12:23 PM Subject: FW: [JBoss-dev] [ jboss-Change Notes-672538 ] Master Configuration Service > this one didn't make it either... > > -----Original Message----- > From: Matt Munz > Sent: Fri 1/24/2003 12:18 PM > To: [EMAIL PROTECTED] > Cc: > Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master Configuration Service > > > David, > > If you will, take a step back with me. Think JMX and not JBoss-JMX. You are >writing a tool to do generic operations on MBeans. This is the purpose of JMX in the first place. Your tool encounters a RW attribute. What assumptions can be made, reasonably? > > Here are my assumptions: > > 1. get the value of the attribute and store it in an object. Do not modify the >object. Set the value of the attribute to the object. No error will occur. > 2. set the attribute to a given value that is not equivalent to the current value. > The behavior / state of the MBean will change in a meaningful way. > > Does the JMX spec enforce these? Perhaps not. Is it nevertheless reasonable to >expect this behavior? I think so. Neither of these assumptions are upheld, however, in the current use of MBeans in JBoss. > > I realize that re-writing mbeans might cause pain for the project. I'm not >suggesting that it should even be done, necessarily, at least not right away. I am, however, trying to reconcile the notion of a RW attribute where writing the value has no effect. Can this be explained simply? > > BTW, I don't see how the lifecycle is related to this particular issue. Perhaps >you could explain this in more depth? > > - Matt ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
