1. Not today, though I think this would be a good feature for the DAS to pick up.
2 a. No, but that would be an interesting capability. Today I think validation would best be performed at the client level. b. It's probably easiest to do this on a case by case basis.. Unfortunately I don't think there's an easy way to undo individual changes (though you can always undo everything using ChangeSummary.undoChanges()). To undo an insert, you can simply delete the DataObject. For property changes, you can use changeSummary.getOldValues() to get the previous values and re-set them. I'm not sure if anything easier is coming in future versions of SDO or not. c. The DAS has some paging capability for situations like this. From your description of your application, it sounds like you may also be able to simply break the app down so that you use several different config files with independent DataGraphs. Brent On 5/11/07, Ron Gavlin <[EMAIL PROTECTED]> wrote:
Greetings, We are considering replacing some of our custom, home-grown DAS' with Tuscany DAS. As a result, I have a few Tuscany DAS questions. 1. Does the Tuscany DAS have any support for JDBC Batch Update/Insert operations? 2. I have a multi-tiered application in which I send a DataGraph of DataObjects from the middle-tier to a client and later receive the updated DataGraph from that client. I would like to apply validation to some of the DataObjects in the DataGraph before the changes are persisted to the database. a. Is there a mechanism for integrating my validation into the DAS' applyChanges() operation to avoid the overhead of traversing the ChangeSummary twice, once by me and once by the DAS? b. When a single DataObject fails validation, what is the best way for me to undo the changes to that particular DataObject so the DAS ignores just those changes and doesn't persist them to the database? c. The DataGraph of changed DataObjects if often large in my application. Also, my custom validation logic is quite expensive. So, I would like to break the DataGraph into multiple "sub-DataGraphs" and execute the validation logic and the DAS' applyChanges() on separate WorkManager threads. I am doing something like that today with my own home-grown DAS that is custom to my trivial data model, whereby the DataGraph is simply a container for a list of DataObjects that map one-to-one to a database table. Thanks in advance for your assistance/insights, - Ron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
