Some food for thought on the mbean system: (Just tell me to shutup and crawl back into my cubicle if you want!)
While reading the thread "current mbean structure confusing" I was thinking about some other issues with mbeans, specifically versioning. In the special purpose app server we developed at my previous company we ran into a problem with upgrades. Our complete system consisted of something similar to mbeans (we developed this before the JMX stuff was around...) running in a simple container. (Sounds familiar? :-)) When we sent a new version of our software to a client (our clients included our own IT) we needed a way for the software to recognize that newer versions of some of the components were available. So we extended our component system to make it aware of its own version number and allowed a special method to perform upgrade tasks (it got the old version number, so it could perform the correct upgrade) I see this type of thing as a very useful extension to the current JMX stuff. Any thoughts on this? Does JMX 1.1 address this? If there is interest, I am willing to seriously look at implementing something like this. Also, since we always upgraded the complete system all at once, we didn't have any need for explicit version checking when computing dependencies, but with a generic server like JBoss, this might be of interest as well. This plays into the whole classloader thing as well, because you could conceivably have two different version of the same mbean that are used by other mbeans. This is probably too complicated, but it *could* be useful. Again, thoughts? --Andrew _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
