commit-classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[commit-cp] [bugs #10799] PropertyEditorSupport::setValue throws excepti


From: Matthew Chadwick
Subject: [commit-cp] [bugs #10799] PropertyEditorSupport::setValue throws exception when oldVal is null
Date: Mon, 25 Oct 2004 16:37:14 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

This mail is an automated notification from the bugs tracker
 of the project: classpath.

/**************************************************************************/
[bugs #10799] Latest Modifications:

Changes by: 
                Matthew Chadwick <address@hidden>
'Date: 
                Mon 10/25/2004 at 20:32 (GMT)

------------------ Additional Follow-up Comments ----------------------------
It appears that old value is also being set inappropriately.  (oldValue = val 
instead of oldValue = this.val).  Better variable names would improve the 
clarity here.






/**************************************************************************/
[bugs #10799] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=10799>
Project: classpath
Submitted by: Matthew Chadwick
On: Mon 10/25/2004 at 20:17

Category:  classpath
Severity:  5 - Average
Resolution:  None
Privacy:  Public
Assigned to:  None
Status:  Open
Platform Version:  None


Summary:  PropertyEditorSupport::setValue throws exception when oldVal is null

Original Submission:  java.beans.PropertyEditorSupport's "public void 
setValue(Object value)" method throws a NullPointerException when oldVal is 
equal to null.  The method should check for cases where the old value is null.  
If both the new and the old values are null, no property change event should be 
fired.  If only the old value is null, a property change event should be fired.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 10/25/2004 at 20:32       By: Matthew Chadwick <mchadwick>
It appears that old value is also being set inappropriately.  (oldValue = val 
instead of oldValue = this.val).  Better variable names would improve the 
clarity here.












For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=10799>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/







reply via email to

[Prev in Thread] Current Thread [Next in Thread]