Are you sure you don't have some old wonder frameworks hiding in ~/Library/Frameworks or something? That call hasn't been on line 189 since about 9 months ago unless I'm reading the git history incorrectly.

Also, use the source :-) Binaries make life more difficult. Source is easier to keep up to date and debug.


On Jan 23, 2013, at 9:49 AM, Jean Pierre Malrieu wrote:

Le 23 janv. 2013 à 00:02, Ramsey Gurley a écrit :

On Jan 22, 2013, at 3:09 PM, Jean Pierre Malrieu wrote:

attempt to assign value to unknown key: 'masterObjectAndRelationshipKey'.
This WOComponent does not have an instance variable of the name masterObjectAndRelationshipKey or _masterObjectAndRelationshipKey, nor a method of the name setMasterObjectAndRelationshipKey or _setMasterObjectAndRelationshipKey
  at com.webobjects.appserver.WOComponent.handleTakeValueForUnboundKey(
     ... skipped 8 stack elements
  at com.webobjects.appserver.WOComponent.setValueForBinding(
  at er.directtoweb.components.ERD2WSwitchComponent.setExtraBindings(

How old is your Wonder? I see setValueForBinding called on line 190 after explicitly checking hasBinding(key) on 189.


My version of Wonder was three month old. I updated with Wonder binaries that are 8 days old (January 14th), and I get the same behavior...