To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=93051
------- Additional comments from [EMAIL PROTECTED] Fri Aug 29 07:37:05 +0000 2008 ------- Classically, no Uno object is allowed to keep a lock while calling out ... means, that we have two bugs here, - the component context keeps its (unsafe env. provided) lock, as well as - the configmgr keeping its lock. If only one kept a lock, there obviously wouldn't a problem ;-) Putting the component context into the "unsafe" environment was a starting point to roll out the threading stuff into the office, I mistakenly thought, that the component context actually does not reach out for other objects. Quick fix is to just "disarm" it by removing the "unsafe" declaration. Plan basically is (as stated somewhere in the wiki), to move all but some office objects into an "unsafe" environment. The ones not to be moved just ensuring some basic parallelism e.g. for I/O or configuration access. I am somehow sure that there are other Uno object implementations keeping locks while calling out, thus I suggest to fix both, the component context as well as the config manager. -> Michael, do you see a chance to release the config manager lock while calling out? --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
