From: Ramsey G. <rg...@sm...> - 2013-01-23 17:14:27
|
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. Ramsey 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(WOComponent.java:1781) >>> ... skipped 8 stack elements >>> at com.webobjects.appserver.WOComponent.setValueForBinding(WOComponent.java:910) >>> at er.directtoweb.components.ERD2WSwitchComponent.setExtraBindings(ERD2WSwitchComponent.java:189) >> >> How old is your Wonder? I see setValueForBinding called on line 190 after explicitly checking hasBinding(key) on 189. >> >> Ramsey > > 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... > > JPM > > > |