JDK-8019346 : Reconsider the namespace for JDK-7188658
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Won't Fix
  • Submitted: 2013-06-28
  • Updated: 2013-10-17
  • Resolved: 2013-10-17
Related Reports
Relates :  
Description
http://mail.openjdk.java.net/pipermail/security-dev/2013-June/007995.html

I'm not crazy about jdk.tls.* as a namespace. 
Comments
Will close. Talk to CCC head, the feeling is now that everything should be jdk.*, it is the one thing that has remained constant through all the company name changes.
17-10-2013

Prefer to close it as not a bug.
30-09-2013

The namespaces are pretty confusing now. Some of the styles had been rejected by CCC. We need to be on the same page what are the proper namespaces for new properties. "sun.security.ssl" should be deprecated, "jdk.tls" will be used instead in the future. Too much styles for JVM properties, ideally, we should only use one out of "javax.net.ssl", "jsse", and "ssl" in the future. There are three kinds of properties: 1. provider private, i.e., SunJSSE private. suggest to use "jdk.tls" 2. provider private, but suggested that third parties should also adhere to the specification. suggest to use "ssl" or "jsse". My preference is "jsse". 3. the properties used in javax.net.ssl, provider shared suggest to use "ssl". "javax.net.ssl" should also be deprecated accordingly.
20-08-2013