Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8250212

Address reliance on default constructors in the JDK (umbrella)

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Other
    • Icon: P4 P4
    • 16
    • 16
    • core-libs
    • None

      A no-arg public constructor is generated by the compiler for a class if it does not declare an explicit constructor. While convenient, this is inappropriate for many kinds of formal classes, both because the constructor will have no javadoc and because the constructor may be unintended.

      For the JDK, classes intended to be used outside of the JDK, public classes in exported packages, should not rely on default constructors.

        1.
        		 Address use of default constructors in com.sun.source.util Sub-task Resolved Joe Darcy  
        2.
        		 Address use of default constructors in java.logging Sub-task Resolved Joe Darcy  
        3.
        		 Address use of default constructors in the javax.script package Sub-task Resolved Joe Darcy  
        4.
        		 Address use of default constructors in the java.util.concurrent Sub-task Resolved Joe Darcy  
        5.
        		 Address reliance on default constructors in java.net Sub-task Resolved Joe Darcy  
        6.
        		 Address reliance on default constructors in security libs Sub-task Resolved Joe Darcy  
        7.
        		 Address reliance on default constructors in javax.sql Sub-task Resolved Joe Darcy  
        8.
        		 Address reliance on default constructors in java.rmi Sub-task Resolved Joe Darcy  
        9.
        		 Address reliance on default constructors in java.management Sub-task Resolved Joe Darcy  
        10.
        		 Address reliance on default constructors in jdk.jdi Sub-task Resolved Joe Darcy  

            darcy Joe Darcy
            darcy Joe Darcy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: