Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hyades-dev] Commiter vote required for M10 check-in


Sorry Joe asked me to send it.  I'll foward it to him to send nex time.

==================================================
Peter Sun
Staff Software Engineer . Rational Software . IBM Software Group
(781) 676-2758 (TEL) . (781) 676-7510 (FAX)




Harm Sluiman <sluiman@xxxxxxxxxx>
Sent by: hyades-dev-admin@xxxxxxxxxxx

05/26/2004 11:36 AM

Please respond to
hyades-dev@xxxxxxxxxxx

To
hyades-dev@xxxxxxxxxxx
cc
Subject
Re: [hyades-dev] Commiter vote required for M10 check-in






Peter please work through Joe the submit defect fixes for approval.


Thanks for your time.
--------------------------------------------------------------------------
Harm Sluiman, STSM,  
phone:905-413-4032   fax: 4920  
cell: 416-432-9754
mailto:sluiman@xxxxxxxxxx
Admin : Gabrielle Chapman chapmaga@xxxxxxxxxx  Tie: 969-2323


Peter Sun <psun@xxxxxxxxxx>
Sent by: hyades-dev-admin@xxxxxxxxxxx

05/26/2004 11:21 AM

Please respond to
hyades-dev

To
hyades-dev@xxxxxxxxxxx
cc
hyades-dev-admin@xxxxxxxxxxx
Subject
[hyades-dev] Commiter vote required for M10 check-in








The following M10 defects require Committer's approval:


Target drop date to cvs:        May 26 afternoon EST

Target regression test date:May 26 afternoon EST

Target candidate drop:        May 27 (pass 2)


Defect 63867
:
bugzilla_63867 --
Datapool Editor: Value class values are not being updated correctly.

Rationale
:

In this release, we are adding support for Display Value Classes which allows consumers to customize the Datapool Editor to handle different editors (for example, a color chooser).  A bug was found by a consumer of the component noting that the values were not being updated correctly.  This was due to a missing call to the Display Value Class API.  This was not an issue for base Hyades because all values are stored as strings and the default string editor always returned the updated value.  The fix involves adding a call to the update method of the display value class and using the updated value.  The fix is currently being tested by the consumer who found the bug (it is not yet checked into CVS).  Without this fix, the feature is basically useless for complex editors whose getValue() does not return the actual value (for example a combo box).


Risk Assessment
:

No API change. Does not impact consumers except that value objects get updated properly.
Low to Medium risk change.



==================================================
Peter Sun
Staff Software Engineer . Rational Software . IBM Software Group
(781) 676-2758 (TEL) . (781) 676-7510 (FAX)


ForwardSourceID:NT0000E9AE    

Back to the top