Unsafe continues to live in Java 9
Since the beginning of work on Java 9, the removal of critical classes from sun. * Packages (understandably, Sun, and later, Oracle claimed that their use is a company's and companies' own risk) was announced, which caused a flurry of criticism and discontent from the community ( for highload solutions for which performance is everything, use the hidden features of the sun. *). The prehistory began 15 years ago with the release of version 1.4 of the language, during which time a large number of libraries, frameworks, applications managed to inject the private code into their own.
That's just not a complete list of projects that everyone has heard: Scala, Kafka, Akka, Hadoop, Cassandra, Hazlecast and others ...
It seems to be news without a year a week, but I constantly have to deal with the fact that people are not up to date and expect wild problems with the new API in java 9 (maybe not without it, of course, however ...)
')
Oddly enough, the developers from both open jdk and Oracle went to the community to meet and the JEP 260 was adopted, in a nutshell: it’s decided to leave some critically important and widely used internal APIs for which there is no replacement yet, however this does not mean that their compatibility will be guaranteed.
Thus, it was decided to keep the following API:
tells us which classes are in the stack call (with the release of java 9, partly possible transition to JEP 259: Stack-Walking API )
Actually master factory for creating objects of reflection
A non-critical API that already has a replacement will be marked as @Deprecated, starting from Java 9, and starting from Java 10, it is derived from the language.
JDK9 Early Access is now available on 02/24/2017 the latest build of b158 ( jdk9.java.net/download , jdk9.java.net/jigsaw ) and if you look inside, you can find all the above listed classes in the jdk.unsupported module, also together found with them:
com.sun.nio.file.ExtendedCopyOption
com.sun.nio.file.ExtendedOpenOption
com.sun.nio.file.ExtendedWatchEventModifier
com.sun.nio.file.SensitivityWatchEventModifier
providing additional features when working with i / o-operations.
Manufacturers have listened to the community, and as a result, the transition from the sun packages. * Promises to be smooth and not critical, and in case of problems, you can sleep and with version 8, I will be happy to answer questions (b.lutovich@socmetr.ru).
That's just not a complete list of projects that everyone has heard: Scala, Kafka, Akka, Hadoop, Cassandra, Hazlecast and others ...
It seems to be news without a year a week, but I constantly have to deal with the fact that people are not up to date and expect wild problems with the new API in java 9 (maybe not without it, of course, however ...)
')
Reality
Oddly enough, the developers from both open jdk and Oracle went to the community to meet and the JEP 260 was adopted, in a nutshell: it’s decided to leave some critically important and widely used internal APIs for which there is no replacement yet, however this does not mean that their compatibility will be guaranteed.
Thus, it was decided to keep the following API:
sun.misc.Signal
sun.misc.SignalHandler
provides support for working with signals (actually IRC), can report an asynchronous event outside the JVM.
sun.misc.Unsafe
It is used to work directly with the memory (they promise that you can partially use the API from JEP 193: Variable Handles , they also say that some operations will be more efficient).
sun.reflect.Reflection :: getCallerClass (int)
tells us which classes are in the stack call (with the release of java 9, partly possible transition to JEP 259: Stack-Walking API )
sun.reflect.ReflectionFactory.newConstructorForSerialization
Actually master factory for creating objects of reflection
A non-critical API that already has a replacement will be marked as @Deprecated, starting from Java 9, and starting from Java 10, it is derived from the language.
JDK9 Early Access is now available on 02/24/2017 the latest build of b158 ( jdk9.java.net/download , jdk9.java.net/jigsaw ) and if you look inside, you can find all the above listed classes in the jdk.unsupported module, also together found with them:
com.sun.nio.file.ExtendedCopyOption
com.sun.nio.file.ExtendedOpenOption
com.sun.nio.file.ExtendedWatchEventModifier
com.sun.nio.file.SensitivityWatchEventModifier
providing additional features when working with i / o-operations.
Total
Manufacturers have listened to the community, and as a result, the transition from the sun packages. * Promises to be smooth and not critical, and in case of problems, you can sleep and with version 8, I will be happy to answer questions (b.lutovich@socmetr.ru).
Source: https://habr.com/ru/post/322840/
All Articles