To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107771 Issue #|107771 Summary|[sw] remove the UnoCallBack Component|Word processor Version|1.0.0 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|programming Assigned to|mst Reported by|mst
------- Additional comments from m...@openoffice.org Fri Dec 18 15:39:04 +0000 2009 ------- During investigation of issue 105557 it turned out that creating uno References from SwModify listeners is inherently not thread-safe. With the unocore locking refactoring work in CWS swunolocking1, the class SwUnoCallBack was removed, because all it did was allow for this unsafe use of its registered listeners; SwDoc::pUnoCallBack is now simply a SwModify. As a consequence, every time a uno object for a ReferenceMark, DocumentIndexMark, or Footnote is required, a new one will be created. This is suboptimal: the uno objects for these should register directly at the corresponding core objects, which should have a weak reference to the uno object, thus allowing for re-use of existing uno objects in a thread-safe way. When this is done, SwDoc::pUnoCallBack can be removed completely. --------------------------------------------------------------------- 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...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
