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. ---------------------------------------------------------------------- >Comment By: Craig Miskell (cmiskell) Date: 2003-02-21 08:08 Message: Logged In: YES user_id=369658 Fair enough, I won't push the issue. ALthough for the record, it's not really a bug in Cayenne as the end behaviour is correct, just inconvenient. ALso, regarding implementation: Could it not be handled in the likes of AbstractBinding or ExpressionBinding, comparing the current value with the new value, or would the overhead of that be prohibitive. (I think WebObjects does something like that in WOAssociation, which is kind of the equiv of Binding). Then all bindings would benefit in one fell swoop ---------------------------------------------------------------------- Comment By: Howard Lewis Ship (hship) Date: 2003-02-21 05:12 Message: Logged In: YES user_id=26816 This means changing all the form element components to perform and read and compare before doing an update. It's doable, but I can't help but think this is asking Tapestry to fix a Cayenne bug. Cayenne could also do this comparison inside the code generated from the model, or handle it internally. ---------------------------------------------------------------------- Comment By: Howard Lewis Ship (hship) Date: 2003-02-21 05:12 Message: Logged In: YES user_id=26816 This means changing all the form element components to perform and read and compare before doing an update. It's doable, but I can't help but think this is asking Tapestry to fix a Cayenne bug. Cayenne could also do this comparison inside the code generated from the model, or handle it internally. ---------------------------------------------------------------------- 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: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
