lang-management modification - it may break customer application? (original) (raw)
Jing LV lvjing at linux.vnet.ibm.com
Thu Jun 30 04:32:04 UTC 2011
- Previous message: hg: jdk8/tl/jdk: 7039182: PPC: NIO: java.io.IOException: Invalid argument in sun.nio.ch.FileDispatcherImpl.read0
- Next message: lang-management modification - it may break customer application?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
I see there is some modifiction in the java.lang.management.ManagementFactory, e.g, newPlatformMXBeanProxy. The LogManager.LOGGING_MXBEAN_NAME in Java7 has been changed and now represents PlatformLoggingMXBean rather than java.util.logging.LoggingMXBean. I understand this is the stradegy to move all MXBean into java.lang.management package. However in JDK6, customers may already use java.lang.management.ManagementFactory.newPlatformMXBeanProxy(someserver, LogManager.LOGGING_MXBEAN_NAME, LoggingMXBean) to get LoggingMXBean and in JDK7 he would meet a IllegalArgumentException. I am wondering if there is a solution to avoid this, e.g, allow it still return LoggingMXBean?
Thanks.
-- Best Regards, Jimmy, Jing LV
- Previous message: hg: jdk8/tl/jdk: 7039182: PPC: NIO: java.io.IOException: Invalid argument in sun.nio.ch.FileDispatcherImpl.read0
- Next message: lang-management modification - it may break customer application?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]