From: Michael H. <mh...@de...> - 2009-06-04 23:19:30
|
Hi: I have some more information on this issue. We are using addObjectToBothSidesOfRelationshipWithKey and removeObjectFromBothSidesOfRelationshipWithKey to set/remove the relationship and to update the inverse relationship. Well in WO 5.4.3 it does not appear to be working correctly? Is Wonder doing anything to fix this issue or working around this issue? We are still using EOEditingContext, maybe using ERXEditingContext would be appropriate? Michael. Michael Hast wrote: > Hi: > > We recently upgraded to WO 5.4.3 with Wonder 5.0.0.9315. The following > sequence of actions throws a > ERXDatabaseContextDelegate$ObjectNotAvailableException. > > 1. Proposal List Page: List proposal objects fetched in editing context > 1 in a table. The list displays attributes as well as one to-many > relationship to TechnicalReviews. > 2. Proposal Edit Page: Press the edit button on the list page to edit a > Proposal which is done in a peer editing context 2. We remove one object > from the to-many relationship to TechnicalReviews and save the changes > to the db. > 3. Return to Proposal List Page: Press the back button on the edit page > which simply returns the previous page WOComponent. That results in the > ERXDatabaseContextDelegate$ObjectNotAvailableException. > > er.extensions.eof.ERXDatabaseContextDelegate$ObjectNotAvailableException: > No com.desertsky.ldrd.shared.model.domain.ReviewTechnical found with > globalID: <ReviewTechnical: [reviewTechnicalId: '17670'] > > at > er.extensions.eof.ERXDatabaseContextDelegate.databaseContextFailedToFetchObject(ERXDatabaseContextDelegate.java:295) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:122) > at com.webobjects.foundation._NSDelegate._perform(_NSDelegate.java:223) > at com.webobjects.foundation._NSDelegate.perform(_NSDelegate.java:167) > at > com.webobjects.eoaccess.EODatabaseContext._fireFault(EODatabaseContext.java:4205) > at > com.webobjects.eoaccess.EOAccessFaultHandler.completeInitializationOfObject(EOAccessFaultHandler.java:89) > at > com.webobjects.eocontrol.EOCustomObject.willRead(EOCustomObject.java:1172) > at > com.webobjects.eocontrol._EOMutableKnownKeyDictionary$Initializer$_GenericRecordBinding.valueInObject(_EOMutableKnownKeyDictionary.java:570) > at > com.webobjects.eocontrol.EOCustomObject.storedValueForKey(EOCustomObject.java:1634) > at > com.desertsky.ldrd.shared.model.domain.auto._ReviewTechnical.dateCreated(_ReviewTechnical.java:78) > > Before upgrading to WO 5.4.3 (from WO 5.3.3) and the Wonder all this was > working. After returning from the edit page, the list page showed the > correct TechnicalReview objects. Has anyone else experienced this? Is > this a WOnder or WebObjects issue? Does anyone have any hints on how to > determine why the list page editing context does not update? > > Michael. -- Tel: (520) 572-9410 Desert Sky Software: www.desertsky.com Specializing in the Development and Hosting of e-Business Applications. |