Did you guys get your issues resolved? I have run into similar problems and have too been left wondering if trading a slight level of effort for a big black box of problems is worth it.
I had the problem of only being able to add one new item and then would get an error. I have auto-sync turned off and had tried both adding to the managed collection and committing, as well as using createItem, and I finally found my problem was that I was not setting the id correctly in the assembler createItem. I refill from the client side and expected it to pickup the new ids but it didn't. After I set the id properly I had a null entry in my managed collection so I went back to refilling anyway. But now I have a problem where the framework sees changes to my object fine before adding a new item, but not after. So first I'd see log lines like Received PropertyChangeEvent: destination: MyObject, property: mappedTargets.0.segmentID, oldValue: 7831, newValue: 7832 But after adding an item those changes do not register on any of my objects (although changes to some other properties still do). Has anyone run into this or can offer help resolving this? charles --- In [email protected], Jeff Vroom <jvr...@...> wrote: > > Yeah, that 'undefined' error is really just the player incorrectly reporting > some error which is thrown up on the stack. If you do not register a fault > handler, it is thrown as an error so that makes sense. > > You have autoCommit set to true so the client is committing after each > property change event which causes a large number of updates. You probably > want to just set autoCommit to false and manually call "commit" after each > change. If calling commit is not desired, maybe you just set up a timer to > call commit periodically if there are any pending changes. > > Jeff > > From: [email protected] [mailto:[email protected]] On > Behalf Of vdeprojects > Sent: Sunday, February 08, 2009 11:06 PM > To: [email protected] > Subject: [flexcoders] Re: LCDS : Managed associations - creating/deleting new > Items > > > It seems that adding a DataConflictEvent.CONFLICT event handler and a > DataServiceFaultEvent.FAULT event handler to the data service can > prevent the uncaught 'undefined' exception. In my case I simply have to > type quickly to run into a data conflict (each keystroke seems to be > sent to the server...). Anyone any idea? >
