Framework to handle CRUD faults in Eclipse [was #7465]
{color:red}
reported by [~vitt] at 2008-07-18
previously known as [trac#76|http://www.textgrid.de/trac/ticket/76] {color}
Currently, CRUD errors (faults) are thrown as IOExceptions as well as passed through the crud plug-in's handleError method, resulting in a (rather crude) error dialog as well as in a log message.
Unfortunately, in prominent cases (like IFile.setContents()) the exceptions are silently caught due to some strange eclipse behaviour. Client's don't realize here that the setContents had failed :-(
Additionally, errors (especially AuthFaultExceptions) may cumulate and thus spam the users with error messages.
As well, we must develop some framework to communicate sensible error messages to the user.
And finally, we should think about some "warning" messages etc. and how they reach the user - cf. [tg:AGArchitektur-Treffen25|http://www.textgrid.de/index.php?id=wiki0&tx_drwiki_pi1\[keyword\]=AGArchitektur-Treffen25] (what happens when adaptors fail?).