Hi Benson On Wed, Feb 9, 2011 at 7:06 PM, Benson Margulies <[email protected]> wrote: > The MBean client API is kind of a pain in the neck. Talking RMI to > contact MBean servers on multiple machines is a really big pain in the > neck. > > If you were sitting down to create a webapp to visualize some > management data, you would perhaps rather write that code in terms of > a JSON-ish data model of the data. than in terms of the MBean API. > > So, our thought was to solve both problems: get rid of the RMI > business by having a service on each machine that exposed the data via > JAX-RS, and be able to code to a less annoying data model. >
Interesting. Something similar to what we have thought about before, back in the old days. Similarly to the unified search experience, one can offer a unified management experience, whereby every important resource supports a _manage query extension and return an HTML form/etc allowing for viewing the statistics and do some more involved tasks. As far as I recall we briefly discussed it on the dev list with some concerns being expressed about the possible complexity associated with the accurate representation of the management data. The idea at a time was to introduce a JAX-RS wrapper (in rt/management-web) which would sit on top of MBeans. > One of my colleagues is likely to post some more specific thoughts > about what he hates about the MBean API. > Cool :-) Cheers, Sergey
