Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #30371 > unrolled thread

replacement for sun.management.jmxremote.ConnectorBootstrap

Started byAndreas Leitgeb <avl@auth.logic.tuwien.ac.at>
First post2014-11-20 20:40 +0000
Last post2014-11-22 00:24 +0000
Articles 3 — 2 participants

Back to article view | Back to comp.lang.java.programmer


Contents

  replacement for sun.management.jmxremote.ConnectorBootstrap Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-11-20 20:40 +0000
    Re: replacement for sun.management.jmxremote.ConnectorBootstrap Jan Burse <janburse@fastmail.fm> - 2014-11-20 22:33 +0100
      Re: replacement for sun.management.jmxremote.ConnectorBootstrap Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-11-22 00:24 +0000

#30371 — replacement for sun.management.jmxremote.ConnectorBootstrap

FromAndreas Leitgeb <avl@auth.logic.tuwien.ac.at>
Date2014-11-20 20:40 +0000
Subjectreplacement for sun.management.jmxremote.ConnectorBootstrap
Message-ID<slrnm6skep.r49.avl@login.logic.tuwien.ac.at>
sun.management.jmxremote.ConnectorBootstrap "Sun proprietary API"

I'd have expected that google would yield hundreds of hits for
the "is Sun proprietary API"-warning that I get, but nothing :-(
A few hits merely have it in some compile-log snippet but discuss
entirely different matters.

Some "legacy" part of a project uses that class, and jdk1.6 started
to complain about it.  If anyone else used that class and found a
replacement, then it seems like he didn't yet write about it anywhere
where google could have picked it up.

Does this ring a bell in anyone here, or will I need to hope that
the warning will remain to be just a warning for long enough, until 
someone else will have to deal with it for that project? ;-)

PS: jmx features are actually used, so it's no dead code.

[toc] | [next] | [standalone]


#30372

FromJan Burse <janburse@fastmail.fm>
Date2014-11-20 22:33 +0100
Message-ID<m4lmo4$3l9$1@news.albasani.net>
In reply to#30371
Hi,

Andreas Leitgeb schrieb:
> PS: jmx features are actually used, so it's no dead code.

They are not available on Android, at least the last
time I looked, I didn't find them.

Bye

[toc] | [prev] | [next] | [standalone]


#30383

FromAndreas Leitgeb <avl@auth.logic.tuwien.ac.at>
Date2014-11-22 00:24 +0000
Message-ID<slrnm6vltd.r49.avl@login.logic.tuwien.ac.at>
In reply to#30372
Jan Burse <janburse@fastmail.fm> wrote:
> Andreas Leitgeb schrieb:
>> PS: jmx features are actually used, so it's no dead code.
> They are not available on Android, at least the last
> time I looked, I didn't find them.

Well, I'm not on Android.

If anyone else has(or had) a need for jmx-stuff on Java SE,
and either found a replacement or still uses it with 1.7
successfully ignoring the warnings, I'd be glad to read...

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.java.programmer


csiph-web