Yes, as long as you return the coerced value, not call set...
Making validate... change data is bad.
On Nov 12, 2009, at 3:32 PM, Travis Britt wrote:
validateValueForKey is safe for coercing user input tho right?
tb
On Nov 12, 2009, at 4:59 PM, David Avendasora wrote:
Nope. This is exactly where you should put this type of thing. If
you put this in the validation methods you'd be asking for trouble.
Dave
On Nov 12, 2009, at 4:49 PM, Ricardo J. Parada wrote:
public void setCpt(String value) {
if (value != null) value = value.toUpperCase();
super.setCpt(value);
}
P.S. I'm using eo-gap generation pattern. So this class extends
the _ class generated by the _WonderEntity.java template.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
This email sent to [email protected]
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
