> > If you are in such a scenario it is imperative that you stop at the > point that your data is broken to limit the scope of the damaged data. > If you don't you will end up with the bad data spreading from system > to system. >
This is an interesting problem and I'm really interested in getting answers here. In my case, I'm not stopping processing but I'm only returning valid instances (in my report context, that is; the domain context is always able to load invalid instances which can then be passed to a form so that the user can correct it). How are you solving this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
