To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=99257





------- Additional comments from [email protected] Wed Feb 18 15:35:49 +0000 
2009 -------
The common.rdb or common_.rdb are locked by the client program (runtests). When
the client starts then it creates the cli-uno bridge in its process, which
bootstraps UNO using the libraries from the office installation. Bootstrapping
UNO includes setting up the service manager, which causes all services rdb
files, such as common.rdb, to be opened. The file will then remain opened as
long as the client runs. When the client restarts OOo then OOo cannot overwrite
the common.rdb, which is still opened by the client. 

This problem has become visible, because OOo is now bundled with a couple of
extensions. Opening a calc document will now lead to a call into the service
manager.
The bug does only affect the cli-uno bridge, AFAIK.

The work around is to use the quickstarter of OOo.

Possible fixes are:

1. Allow adding / removing services of the loaded rdb files

2. Invent  another mechanism of how the extension services  are registered

3. Write a real cli-uno remote bridge. The current bridge is actually an
inprocess bridge, which was intended for using cli-uno components.

All three solutions are time consuming and to risky for 3.1. I therefore suggest
to retarget this issues as long as OF can verify that the workaround works.




---------------------------------------------------------------------
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]

Reply via email to