Costin Manolache wrote:
Remy Maucherat wrote:

If the question is about using JMX1.2 - it was alredy proposed, and it
seems nobody objected ( but nobody did it either ). If you want to do
that - all you need is update the mbean descriptors, and change all the
arrays to use the JNI names ( [Ljava.lang.String; instead of
java.lang.String[] ). And of course - fix download to get jmxri instead
of mx4j.
When MX4J implements 1.2, we'll switch back.
I'm using JMXRI1.2 - and so far it works very nice.
Regarding the registration listener: there are 2 issues you need to be carefull. First, it would be good if the code is independent of
the load order - i.e. listen for notifications but also do a query for
the existing objects. You can do that using JMX query, or by
using the attributes. After you take care of the existing mappings, you can start listening for registration - you can do both with plain
JMX1.1.
Speaking of which, I'm missing a registration for the hosts (I don't know if it's defined in JSR 77).
Could we add some custom attributes on the object name for wrapper (giving the mapping), as well as the host registration, and still comply with the spec (I'd say yes, but ...) ?

Thanks,
Remy


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to