A couple points re: re-use of existing JMX-based plugins:
1) We have to be very careful that no operations that are meant to be
performed via the domain API are instead available via some side
mechanism. So that means some if we keep an existing plugin, some of its
functionality needs to be disabled. (I know you know this; just putting
it down in this thread.)
2) The domain API is meant to expose metrics and management operations,
and for it to be complete, most things exposed in AS 6 over JMX by
subsystems like HQ really should be available via the domain API -- even
if one client, the console plugin, doesn't use the domain API to access
them. So I want to avoid us thinking that re-using existing plugins will
avoid the need to expose stuff via the domain API.
On 1/3/11 6:47 AM, Heiko W.Rupp wrote:
Hey,
happy new year.
I've posted a first architecture draft at
http://www.rhq-project.org/display/RHQ/AS7+console
Please comment on it.
Heiko
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat