We're using FDS on our project, and we're using a single DataStore with autoCommit=false on all of our DataServices. This way, we're able to have a single, application-wide save button to commit all the latest changes. This save button is enabled based upon on the DataStores' commitRequired property.
In a few of my VOs, I have properties that do not have a corresponding property in my server-side POJO. The reson is that these properties are strictly used for keeping track of client-side state and are not persisted in our database. My problem is this: setting these properties on the client causes commitRequired to become true on our DataStore. This is sort of annyoing, as there really are no changes that need to be persisted. Of course, hitting the save button sends back the objects to the server where they are simply ignored because nothing has actually changed on them. So is there a way that I can force these properties to be ignored? Is there some type of undocumented metadata tag that I'm missing? I seem to remember something similar in Flex 1.5 to make serialization ignore a property, but this is a slightly different case. Jim -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
