JDK-4134085 : ListDataEvent class missing paramString() method
  • Type: Bug
  • Status: Resolved
  • Resolution: Fixed
  • Component: client-libs
  • Sub-Component: javax.swing
  • Priority: P4
  • Affected Version: 1.2.0
  • OS: generic
  • CPU: generic
  • Submit Date: 1998-04-30
  • Updated Date: 2000-03-22
  • Resolved Date: 2000-03-22
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.
Other
1.4.0 betaResolved
Description
Abstract:       ListDataEvent class missing paramString() method

Description:    ListDataEvent details are not present upon printing
                the event...  

                For example:

                    list.addListDataListener (new ListDataListener () {
                        public void printEvent (ListDataEvent e) {
                            System.out.println (e);
                        }
                    }

Swing version:  1.0.1

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
2004-06-14

WORK AROUND Workaround: Can print out the event details manually...
2004-06-11

PUBLIC COMMENTS The toString() method of ListDataEvent will need to be overridden. michael.albers@Eng 2000-03-08
2000-03-08

SUGGESTED FIX Override the toString() method of ListDataEvent. michael.albers@Eng 2000-03-08
2000-03-08

EVALUATION ListDataEvent should add list-event-specifc information when it gets converted to a string. tom.santos@eng 1998-05-27 Yeah, this just needs a paramString() method added to it. However, there are only three member variable in this class. All three of them are accessible via getter methods. The convenience of being able to do a toString() is nice here but doing it manually is an extremely viable workaround. Plus, the addition of the paramString() method will constitute an API change (for some lame reason) which is not allowed right now. michael.albers@Eng 1999-07-01
1999-07-01