• 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
New NSKeyValueCoding in 5.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New NSKeyValueCoding in 5.4


  • Subject: New NSKeyValueCoding in 5.4
  • From: Alexander Spohr <email@hidden>
  • Date: Tue, 11 Dec 2007 15:58:32 +0100

FYI:

The behavior of NSKeyValueCoding.DefaultImplementation has changed.

If you used subclasses of Maps and wanted to add instance variables to be used by NSKeyValueCoding the following was a valid method inside your MapSubclass:

public Object valueForKey(String key) {
Object retVal = null;
try {
retVal = NSKeyValueCoding.DefaultImplementation.valueForKey(this, key);
} catch (Exception e) {
retVal = this.get(key);
}
return retVal;
}


This behavior does not work anymore!

If NSKeyValueCoding.DefaultImplementation gets a Map it forwards the request to MapImplementation which ONLY asks for map.get(key) and returns null if there is no such key. You can not get to any instance- variable using NSKeyValueCoding anymore as all Maps are redirected to the new (non-documented) MapImplementation.valueForKey().

	atze

_______________________________________________
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: New NSKeyValueCoding in 5.4
      • From: Ryan Klems <email@hidden>
  • Prev by Date: Re: WOCheckbox strangeness
  • Next by Date: Re: wolips / webobjects build question
  • Previous by thread: Embedded Split Install Script
  • Next by thread: Re: New NSKeyValueCoding in 5.4
  • Index(es):
    • Date
    • Thread