JDK-4883196 : Five JTable methods should not declare @throws IllegalArgumentException
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.2.2,1.3.1,1.4.0,5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_2.6
  • CPU: generic,sparc
  • Submitted: 2003-06-24
  • Updated: 2017-05-16
  • Resolved: 2003-07-26
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 Availabitlity Release.

To download the current JDK release, click here.
5.0 tigerFixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
There are five methods in JTable that are documented to throw an IllegalArgumentException for certain input. These methods however, have never been implemented to throw for that input. There are two possible fixes: to change the implementation to throw the exception, or to remove the documentation that mentions it. An analysis of the methods indicates that rather than throwing an exception, they instead return false, which is an acceptable result. Since developers may rely on this behavior, the best approach is to remove the invalid documentation.

Note that this bug was created to consolidate four separate bugs. Here's the bugs and the methods that they are filed on:

Bug         Method

(4465795)   isRowSelected(int)
(4465792)   isColumnSelected(int)
(4465732)   isCellSelected(int)
(4464167)   editCellAt(int, int)
(4464167)   editCellAt(int, int, EventObject)

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b13 VERIFIED IN: 1.5

EVALUATION I filed this and I'm fixing it. Filing a request to change the docs. ###@###.### 2003-06-24 This is now fixed. ###@###.### 2003-07-08