Revision as of 10:09, 22 May 2015 by Anebuzelsky (Talk | contribs)


Internal JDK APIs Unavailable In Java 9

With Java 9 coming we have to prepare for several big changes which will affect NetBeans and might break the code. One such change is that bunch of internal APIs from JDK 8 and older will become really JDK internal and will not be accessible from NetBeans. Internal APIs will not be accessible when JDK 9 module boundaries will be in place. We have to therefore replace these APIs with new one. This document serves for tracking NetBeans packages which are affected, list some already published replacement/workarounds. We will use this doc to make sure NetBeans version supposed to be running on Java 9 will be ready on time re internal API usage.

jdeps tool

We used jdeps tool to search for what Java internal APIs we are using. It lists also some examples how to replace obsolete internal APIs with new public ones. It is recommended that every NetBeans module developer runs jdeps on his modules and does not depend solely on this table.

sun.* packages

APIs under sun.* will be Java private one and will not be accessible from within NetBeans sources. Here is the list of NetBeans modules and what sun.* packages were found.

Owner Resolved/Comment NetBeans module Internal Java API being used dlight.remote, sun.swing.FilePane, un.swing.WindowsPlacesBar glassfish.common sun.misc.BASE64Encoder, jconsole sun.jvmstat.monitor.*,, kenai sun.misc.BASE64Encoder lib.profiler sun.jvmstat.monitor.* o.n.swing.dirchooser openide.filesystems, php.dbgp sun.misc.BASE64Encoder profiler.heapwalker sun.misc.VM profiler.snaptracer sun.swing.plaf.synth.SynthIcon, sun.awt.X11.XToolkit, sun.awt.X11.XWM, sun.swing.plaf.synth.SynthIcon debugger.jpda sun.reflect.DelegatingClassLoader, sun.font.AttributeMap, sun.reflect.ReflectionFactory, sun.awt.X11.XAwtState, sun.awt.X11.XBaseWindow, sun.awt.X11.XToolkit, sun.awt.X11.XAtom debugger.jpda.visual sun.misc.Launcher$AppClassLoader editor sun.awt.AppContext lib.profiler.charts sun.swing.SwingUtilities2 o.n.bootstrap sun.awt.AppContext o.n.swing.dirchooser sun.swing.WindowsPlacesBar, o.n.swing.plaf sun.swing.plaf.synth.SynthUI openide.explorer sun.beans.editors.EnumEditor openide.text, openide.util sun.awt.AppContext profiler.oql sun.misc.Ref sampler spi.editor.hints sun.swing.plaf.synth.SynthIcon traceio sun.misc.IoTrace web.jspparser sun.misc.SharedSecrets, sun.misc.ClassLoaderUtil

com.sun.* packages

Some packages from com.sun will become public API in Java 9. These are:

  • com.sun.source.*
  • com.sun.jdi
  •* is exported, subpackages will be internal

As the source of intermediate info about what packages will be exported from Java 9 you can refer to modules.xml for Java 9 modules being API. This info/mechanism can change (modules.xml can be replaced by something different) once Java 9 implementation proceeds further to Feature complete and release. Following table lists NetBeans modules which utilizes com.sun.* internal APIs which will be internal in Java 9. com.sun.source usage and com.sun.jdi usage were removed from this list.

Owner Resolved/Comment NetBeans module Internal Java API being used javacard.* com.sun.javacard.* jconsole com.sun.jmx.* web.el com.sun.el.parser.* web.jsf.editor com.sun.faces.* websvc.**,*, com.sun.xml.rpc.* java.source* - Listed for completness, nbjavac contains this. (only this package exported, subpackages are not) debugger.jpda.visual* apisupport.feedreader com.sun.syndication.* debugger.jpda.visual com.sun.javafx.runtime.* core.browser.webview com.sun.javafx.scene.web.Debugger debugger.jpda.visual* o.n.swing.plaf, o.n.bootstrap com.sun.jnlp.JNLPClassLoader core.startup,,
identity.profile.api com.sun.identity.* cnd.modelimpl*,* deployment.deviceanywhere


It should be be possible to use reflection to call Java internal APIs even after module boundaries will be in place. It will be likely necessary to call setAccessible(true) for elements which needs to be called via reflection. At this moment it is not 100% confirmed it will work this way or setAccessible(true) will be needed.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo