Issue 67560 - rejecting types due to incompatibility ... differrent number of types.
Summary: rejecting types due to incompatibility ... differrent number of types.
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2006-07-19 13:58 UTC by
Modified: 2013-02-07 21:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 2006-07-19 13:58:40 UTC
take the extensions from issue 66948
install them,
then install one of the new ones, e.g from issue 66005
-> message comes up, extension is not enabled.

The message comes also up, when i first install the .oxt and then
Comment 1 joachim.lingner 2006-07-19 14:06:34 UTC
Comment 2 joachim.lingner 2006-07-26 14:55:53 UTC
The error is justified. Both extensions bring a new interface with the same
name, but they have different number of methods. Interface names must be unique.
This has been violated in this case.
However, when running unopkg then it was possible to install the second
extension after unopkg was started a second time. This is a bug.
Comment 3 joachim.lingner 2006-07-26 15:33:04 UTC
When unopkg is started and a office is runnging than it connects to it and uses
its UNO environment. If no office is running then it bootstraps a minimal UNO
environment (desktop/source/pkgchk/unopkg_misc.cxx, getUNO). Then the type rdbs
of the installed extensions are not added to the TypeDescriptionManager.

We could change the code in getUNO so that in case no office is running UNO is
completely bootstrapped. In many places there is code that checks if the office
is running (::dp_misc::office_is_running() ) and follows different code path.
This code may expect the standalone UNO environment, rather then the full
All these places have to be thouroughly investigated, and adjusted if necessary.

Comment 4 Martin Hollmichel 2007-12-07 13:00:45 UTC
set target to 3.x according to
Comment 5 joachim.lingner 2009-07-22 11:26:42 UTC
Now in DEV300m51 (pre OOo 3.2) there is the error output from unopkg:
An error occurred while enabling: t.rdb
and the extension is not installed.

There should be at least an error message from the exception, indicating the
problem with the incompatible interface.