Need some advice on handling EO validation errors
Need some advice on handling EO validation errors
- Subject: Need some advice on handling EO validation errors
- From: Greg Lappen <email@hidden>
- Date: Fri, 07 Dec 2007 10:48:11 -0500
Hi all,
I just recently ran into an issue where my application tried to save
a new object to the database, the save failed, and every subsequent
save failed with the same error. It seems that WebObjects maintains
a queue of updates/saves to write to the database, and when one
fails, it essentially clogs up the queue because WO keeps trying to
save it eveytime someone calls saveChanges() on an editing context.
What I'd like to do is set up a global exception handler in my
application that runs whenever an exception is not caught by my code,
and in that error handler I want to reset the whole EnterpriseObject
stack - the cache, the update/save queue, everything - so that other
work in the application can continue and not worry about cache
corruption or anything like that.
Is this possible to do? Anyone know how to do it?
Thanks so much for any help.
Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden