- 
    Enhancement 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    16
- 
        b17
                    The situation discussed in JDK-8251921, a class that is part of the formal API but has at least some protected rather than public, containing types, occurs for several AWT classes:
java.awt.Component.AccessibleAWTComponent.AccessibleAWTComponentHandler java.awt.Component.AccessibleAWTComponent.AccessibleAWTFocusHandler
java.awt.Container.AccessibleAWTContainer.AccessibleContainerHandler
This pattern doesn't seem to appear elsewhere in the JDK.
A fix for issue can be a follow-up toJDK-8250856.
            
java.awt.Component.AccessibleAWTComponent.AccessibleAWTComponentHandler java.awt.Component.AccessibleAWTComponent.AccessibleAWTFocusHandler
java.awt.Container.AccessibleAWTContainer.AccessibleContainerHandler
This pattern doesn't seem to appear elsewhere in the JDK.
A fix for issue can be a follow-up to
- csr for
- 
                    JDK-8253450 AWT Accessibility API nested classes rely on default constructors -           
- Closed
 
-         
- relates to
- 
                    JDK-8250639 ☂ Address reliance on default constructors in the java.desktop module -           
- Open
 
-         
- 
                    JDK-8250856 Address reliance on default constructors in the AWT APIs -           
- Resolved
 
-         
- 
                    JDK-8251921 Expand default constructor warning to cover more cases -           
- Resolved
 
-         
- 
                    JDK-8253753 Enable default constructor warning in client modules -           
- Resolved
 
-         
             (2 links to)
        
     
        