• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Is this a violation of the EOF commandment?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this a violation of the EOF commandment?


  • Subject: Re: Is this a violation of the EOF commandment?
  • From: Ramsey Lee Gurley <email@hidden>
  • Date: Thu, 12 Nov 2009 21:13:52 -0500

In this case though, he would be changing the value passed.  It is my understanding from the javadocs that this is what validateKey methods are for, explicitly.

http://developer.apple.com/legacy/mac/library/documentation/InternetWeb/Reference/WO542Reference/com/webobjects/foundation/NSValidation.html

They even put 'coerce' in bold text.  This certainly wouldn't be the first time Apple's WO docs were wrong, but the way that documentation reads, it seems coercing the value passed is one of the primary reasons the method exists.

I'll be honest and say I find this particular commandment confusing.  I can understand not wanting to change the value if it is an EO (validateRelationship), but I'm not clear on how changing the value passed would confuse EOF.  The fact that validateKey is being called on an attribute would indicate that EOF knows the object has been changed.  Is it perhaps the difference between being inserted vs updated that causes the problem?

Ramsey

On Nov 12, 2009, at 6:35 PM, Chuck Hill wrote:

> 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@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> --
> 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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Is this a violation of the EOF commandment?
      • From: Chuck Hill <email@hidden>
References: 
 >Is this a violation of the EOF commandment? (From: "Ricardo J. Parada" <email@hidden>)
 >Re: Is this a violation of the EOF commandment? (From: David Avendasora <email@hidden>)
 >Re: Is this a violation of the EOF commandment? (From: Travis Britt <email@hidden>)
 >Re: Is this a violation of the EOF commandment? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: My Eclipse keeps running out of memory
  • Next by Date: Re: Is this a violation of the EOF commandment?
  • Previous by thread: Re: Is this a violation of the EOF commandment?
  • Next by thread: Re: Is this a violation of the EOF commandment?
  • Index(es):
    • Date
    • Thread