On 21/10/2016 08:08, Peter Levart wrote:
:
Otherwise I think it is a good strategy to give frameworks limited
access to selected private methods targeted for a special purpose -
serialization in this case, instead of opening the doors for generic
reflection (via setAccessible). It just feels a little strange that
this is new API in an "unsupported" module which destiny is to
eventually "fade-away" once required functionality appears in a
supported way. What is the message?
Custom serialization libraries have always had to use ReflectionFactory
so the message and they'll have to use it more in order to work with
serializable types in modules using strong encapsaultion. The plan is to
update ReflectionFactory in a JDK 8 update soon, assuming the jdk8u
maintainers approve. It might seem strange to be doing this but it's way
too late in JDK 9 to be taking on another serialization project.
-Alan
