JDK-4730023 : Suggest calling superclass if overriding removeNotify
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-08-12
  • Updated: 2003-10-23
  • Resolved: 2003-10-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b26Fixed
Related Reports
Relates :  
JDK-4289940 - Can't dispose InputContext while it's active
Description
4289940 records a problem with exceptions thrown during disposal, e.g.

Exception during disposal:
                  java.lang.reflect.InvocationTargetException: java.lang.IllegalStateException: 
                  Can't dispose InputContext while it's active 

We should modify the docs for Component.removeNotify to say that client code 
overriding this method should have a call to super.removeNotify as the first 
line of the overriding method (as described in the evaluation for 4289940).
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic tiger-beta FIXED IN: tiger tiger-beta INTEGRATED IN: tiger-b26 tiger-beta
14-06-2004
PUBLIC COMMENTS .
10-06-2004
EVALUATION Fix for tiger. ###@###.### 2003-01-14 Fixed for tiger. ###@###.### 2003-09-17
14-01-2003