If we head down the JMX before Java-interfaces road, we may as well throw away Avalon. It is better that we stick to A-F and automagic wrapping of JMX capability by one of our containers.
Yes, this is an interesting solution, i thought about that too. Basically make our containers be able to run JMX and expose as JMX but not necessarily *be* JMX-based.
It is what Phoenix does. I'm going to take a guess that Merlin does too.
- Paul
-- http://www.thoughtworks.com -> The art of heavy lifting. Home for many Agile practicing, Open Source activists...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
