[ tapestry-Feature Requests-684237 ] Smarter property setting

Feature Requests item #684237, was opened at 2003-02-11 11:33
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=684237&group_id=4754

Category: framework
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Craig Miskell (cmiskell)
Assigned to: Nobody/Anonymous (nobody)
Summary: Smarter property setting

Initial Comment:
I'd like to see the property setting code get a little
smarter when setting, namely checking that the value
about to be set is not the same (equals()) the current
value.  If it is, the set should not be called. 
As justification:  In our app, we're using Cayenne as
the persistence layer.  We have a form with fields that
whose values are directly hooked up to the properties
of the Cayenne DataObjects.  However, when the form is
submitted, Tapestry flits through the form fields and
sets all the properties that were exposed in the form.
 Cayenne then thinks that the object has changed, and
has to do some not insignificant processing to
determine that it hasn't really changed.  
Yes, we have other options (modify cayenne, check
ourselves), but it seems to me that this change could
be beneficial in a number of situations other than just
ours.    

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=684237&group_id=4754


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com