Cannot add user-defined "UNO RDB Type Library" as Extension

Help with installation and general system troubleshooting questions concerning the office suite LibreOffice.
Post Reply
User avatar
gurfle
Posts: 67
Joined: Wed Dec 02, 2009 5:40 am

Cannot add user-defined "UNO RDB Type Library" as Extension

Post by gurfle »

Whenever I try to add a self-made "UNO RDB Type Library", as an Extension, the attempt always fails with this message:

(com.sun.star.uno.RuntimeException) { { Message = "com.sun.star.DeploymentException: an error occured during file opening", Context = (com.sun.star.uno.XInterface) @0 } }

I am running on an AntiX M11 system with the following version of libreoffice:

LibreOffice 3.4.3
OOO340m1 (Build:302)
Debian package 1:3.4.3-3

I recompile and merge into a registry file the following test IDL type definition (which can be added just fine as an extension to Openoffice 3.2):

Code: Select all

#ifndef __names_nick_openoffice_xpythoncomponents_idl__
#define __names_nick_openoffice_xpythoncomponents_idl__

module names { module nick { module openoffice {

    interface XOwnArray
    {
       [attribute] any Values;
    };

    interface XArgument
    {
       [attribute] double target;
       [attribute] double init;
       [attribute] double size;
       [attribute] long nitt;

       [attribute] sequence<double> x;
       [attribute] sequence<double> f;
       [attribute] short side;
       [attribute] short mode;
       [attribute] double lastx;
    };


    interface XFirst
    {
       [attribute] any thing;
       any thingplus23(  );
    };

    interface XFirstFull
    {
       [attribute] any thing;
       any thingplus23(  );
    };

// I think this is needed for "Full" Java (using uno-skeletonmaker) - but NOT Python - Implementation
//    service SFirstFull: XFirstFull {
//
//    };

}; }; };
#endif
That the identification "names_nick_openoffice_xpythoncomponents_idl" still contains "openoffice" should not matter, as that name can be defined arbitrarily.

Here is the script that generates the rdb file from the above code:

Code: Select all

idlc -w -cid -I /usr/share/idl/libreoffice $1.idl
if [ $? -ne 0 ]
then
  exit
fi
rm -f $1.rdb
regmerge -v $1.rdb /UCR $1.urd
rm -f $1.urd
Perhaps the mergeKeyName "/UCR" needs to be altered for libreoffice?

The messages from the script do not indicate any problem:

Code: Select all

Compiling: PythonOOComponents.idl
merging registry "PythonOOComponents.urd" under key "/UCR" in registry "PythonOOComponents.rdb".
However selecting the resulting rdb file from Tools -> Extension Manager... -> Add...
always yields the error I show at the start of this post.
I would like to get this to work in libreoffice. Anybody know how?

Thanks, Nick
Last edited by gurfle on Sat Oct 15, 2011 11:21 pm, edited 2 times in total.
Nicholas Dreyer
AMD sempron 3.4GHz, 1G RAM, nForce3-250Gb motherboard

AntiX M11
LibreOffice 3.4.3

Posts prior to Aug. 18, 2011 referenced
Linux Debian (lenny-backports or squeeze)
OpenOffice 3.2.1
User avatar
gurfle
Posts: 67
Joined: Wed Dec 02, 2009 5:40 am

Re: Cannot add user-defined "UNO RDB Type Library" as Extens

Post by gurfle »

gurfle wrote:I would like to get this to work in libreoffice. Anybody know how?
Turns out this problem is a result of the OpenOffice upgrade from 3.2 to 3.3, much of which was taken on by LibreOffice (at least the 3.3 and 3.4 LibreOffice versions I have been working on).

I will post this again under OpenOffice forum.

EDIT: See response by hanya there: http://user.services.openoffice.org/en/ ... 10#p205700.
Nicholas Dreyer
AMD sempron 3.4GHz, 1G RAM, nForce3-250Gb motherboard

AntiX M11
LibreOffice 3.4.3

Posts prior to Aug. 18, 2011 referenced
Linux Debian (lenny-backports or squeeze)
OpenOffice 3.2.1
Post Reply