Re: ERModernLook: nested embedded edition of to-many relationships

Maybe my previous wonder version was older than I thought (cannot tell until I go back to my time machine backup).
But I did upgrade and get the same error (see stack trace below). I am not the only one facing this sort of problem I am afraid (I can see two messages by other users in my mailbox mentioning this masterObjectAndRelationshipKey pb).

I agree that I should use source. I am just afraid of a cluttered workspace (I already have to many projects). Is it possible to organize the project navigation view so that one does not see all Wonder frameworks there (a filter?). Another question: when you import wonder source, you set wonder frameworks as dependent frameworks or you still rely on the built version of the frameworks?

JPM

The stack trace for a pretty current version of Wonder:

UnknownKeyException: [<er.directtoweb.embed.ERXD2WEditRelationship name: er.directtoweb.embed.ERXD2WEditRelationship subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0 = <er.directtoweb.components.ERD2WSwitchComponent name: er.directtoweb.components.ERD2WSwitchComponent subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0 = <er.modern.look.pages.ERMODEditRelationshipPage name: er.modern.look.pages.ERMODEditRelationshipPage subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0 = <er.modern.directtoweb.components.repetitions.ERMDReducedListPageRepetition name: er.modern.directtoweb.components.repetitions.ERMDReducedListPageRepetition subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0.1.0.1.5.1.0.1.0 = <er.modern.directtoweb.components.buttons.ERMDInspectButton name: er.modern.directtoweb.components.buttons.ERMDInspectButton subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0.1.0.1.5.1.0.1.0.0 = <er.coolcomponents.CCSmartAjaxButton name: er.coolcomponents.CCSmartAjaxButton subcomponents: null >; } >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0.1.0.1.5.1.1.1.1 = <er.modern.directtoweb.components.buttons.ERMDEditButton name: er.modern.directtoweb.components.buttons.ERMDEditButton subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0.1.0.1.5.1.1.1.1.1 = <er.coolcomponents.CCSmartAjaxButton name: er.coolcomponents.CCSmartAjaxButton subcomponents: null >; } >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.1.3.1.0.1.0.1.5.1.2.1.2 = <er.modern.directtoweb.components.buttons.ERMDRemoveRelatedButton name: er.modern.directtoweb.components.buttons.ERMDRemoveRelatedButton subcomponents: null >; } >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.1 = <er.directtoweb.components.ERD2WExtraDisplayPropertyKeysComponent name: er.directtoweb.components.ERD2WExtraDisplayPropertyKeysComponent subcomponents: null >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.5.1.3.1 = <er.coolcomponents.CCSmartAjaxButton name: er.coolcomponents.CCSmartAjaxButton subcomponents: null >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.3.5.1.5.1 = <er.coolcomponents.CCSmartAjaxButton name: er.coolcomponents.CCSmartAjaxButton subcomponents: null >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1 = <er.modern.look.components.ERMODRequiredWrapper name: er.modern.look.components.ERMODRequiredWrapper subcomponents: {0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.0 = <er.directtoweb.components.ERDDebuggingHelp name: er.directtoweb.components.ERDDebuggingHelp subcomponents: null >; } >; 0.3.5.1.2.3.0.1.0.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.9.0.0.0.1.0.1.2.3.1.0.3.3.3.0.1.0.1.3.0.1.3.1.0.0.0.0.0.1.2.3.1.0.3.11 = <er.directtoweb.components.ERD2WExtraDisplayPropertyKeysComponent name: er.directtoweb.components.ERD2WExtraDisplayPropertyKeysComponent subcomponents: null >; } >; } >; } > takeValueForKey()]: 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:190)
     ... skipped 11 stack elements
  at com.webobjects.appserver.WOComponent._doPushValuesUp(WOComponent.java:558)
  at com.webobjects.appserver.WOComponent.pushValuesToParent(WOComponent.java:535)
     ... skipped 101 stack elements
  at er.ajax.AjaxUpdateContainer.handleRequest(AjaxUpdateContainer.java:266)
     ... skipped 105 stack elements
  at er.ajax.AjaxResponse.generateResponse(AjaxResponse.java:67)
     ... skipped 5 stack elements
  at er.ajax.AjaxRequestHandler.handleRequest(AjaxRequestHandler.java:20)
  ... skipped 6 stack elements




Le 23 janv. 2013 à 18:14, Ramsey Gurley a écrit :

> 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
>> 
>> 
>> 
>

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d

_______________________________________________
Wonder-disc mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wonder-disc