Re: General question: sun package -> jdk package?

> On 20 Dec 2015, at 19:46, Joel Borggrén-Franck > wrote: > > Do you know if it is only newConstructorForSerialization? That is our understanding. > Is it worth > keeping a minimal ReflectionFactory in sun.reflect that only exposes > that? That is the current

Re: General question: sun package -> jdk package?

Do you know if it is only newConstructorForSerialization? Is it worth keeping a minimal ReflectionFactory in sun.reflect that only exposes that? On Wed, Dec 16, 2015 at 1:22 PM, Chris Hegarty wrote: > On 15/12/15 18:56, Joel Borggrén-Franck wrote: >> >> Hi Chris, >> >>

Re: General question: sun package -> jdk package?

On 15/12/15 18:56, Joel Borggrén-Franck wrote: Hi Chris, I'm somewhat surprised to see ReflectionFactory on that list. Can you share more details around its external use? ReflectionFactory.newConstructorForSerialization is used by several popular third party serialization, mocking, proxying,

Re: General question: sun package -> jdk package?

2015/12/15 7:09 -0800, Paul Benedict : > I have a general question prompted by the many classes moved from sun.* to > jdk.*. Once JDK 9 delivers on the Module System and internals are no longer > exposed, is it planned to eventually migrate away from the sun.* legacy >

Re: General question: sun package -> jdk package?

Hi Chris, I'm somewhat surprised to see ReflectionFactory on that list. Can you share more details around its external use? cheers /Joel On Tue, 15 Dec 2015 at 16:15 Chris Hegarty wrote: > Paul, > > I cannot address your general question, but I guess it might be

Re: General question: sun package -> jdk package?

I only asked out of curiosity. There seemed to be a migration trend, but I didn't know what the intent was. I understand a name is just a name, but I personally do like seeing the vestiges of "sun" being replaced with something more universal. Cheers, Paul On Tue, Dec 15, 2015 at 1:48 PM,

General question: sun package -> jdk package?

I have a general question prompted by the many classes moved from sun.* to jdk.*. Once JDK 9 delivers on the Module System and internals are no longer exposed, is it planned to eventually migrate away from the sun.* legacy namespace in later JDK versions? Cheers, Paul

Re: General question: sun package -> jdk package?

Paul, I cannot address your general question, but I guess it might be motivated by some of my recent preparatory work for JEP 260 [1]. This JEP proposes to expose a small number of critical API’s that are in the sun.misc and sun.reflect namespace. Anything not deemed critical should be removed