To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108734
------- Additional comments from a...@openoffice.org Mon May 17 07:20:33 +0000
2010 -------
... good question. Current implementation uses a non consistent error handling.
Autorecovery itself runs most the time in "error land" where every call can be
the last one .-) So its not an easy task to find the right strategy.
Please have a look at line 1357 (method implts_flushConfigItem())
if (nRetry <= GIVE_UP_RETRY)
throw ex; // force stacktrace to know if there exist might other reasons, why
an AutoSave can fail !!!
Here I wish to use exceptions to produce a stacktrace to see whats happen in
real. But then catch(Exception(){/*do nothing*/} is wrong.
We should ask ourself first:
a)
Will autorecovery catch ALL exceptions and ignore them because we wish
not to crash in general.
b)
Can autorecovery ignore all exceptions to get a stacktrace to see whats happen.
Currently I tend to a) ... but then we will NEVER get a stacktrace from that
code any more.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
