--- On Thu 06/01, Christopher Lamey < [EMAIL PROTECTED] > wrote: > FWIW, BatchUpdateException is thrown if there's an exception during a > batch update and has enough info for me to figure out what broke when.
I'd be interested to find out more how it works out for you. Say, a batch has 10K records. 300 of them may fail, for various reasons. How do you figure out *why* those records failed? Do you run your batch 300 times, fixing one record at a time? Say, you need to give feedback to a 3rd party about failed records and the reasons, how do you do that? Also, when one of the records fails, the whole batch will be rolled back. Suppose, some records cannot be fixed but you still want "good" records to be imported. How do you deal with that? Regards, _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com
