[Libreoffice-bugs] [Bug 31229] New: The bootstrap function of the LibO API functionality doesn't work

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=31229

           Summary: The bootstrap function of the LibO API functionality
                    doesn't work
           Product: LibreOffice
           Version: unspecified
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libreoffice
        AssignedTo: libreoffice-bugs at lists.freedesktop.org
        ReportedBy: giuseppe.castagno at acca-esse.eu


These two features described on OOo DevGuide:
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Java/Transparent_Use_of_Office_UNO_Components#Finding_a_UNO_Installation
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/C%2B%2B/Transparent_Use_of_Office_UNO_Components#Finding_a_UNO_Installation

At the moment for LibO don't work as described.

Only the possibility with the added parameters will work; that is,for Java
binding you need to use:

java -Dcom.sun.star.lib.loader.unopath=/opt/libreoffice/program -jar
SimpleBootstrap_java.jar

and for C++ binding you need to use these two steps:

setenv UNO_PATH /opt/libreoffice/program
./SimpleBootstrap_cpp

whereas the automatic search for an installed LibO installation won't work in
both cases, e.g for Java:

java -jar SimpleBootstrap_java.jar

and for C++

./SimpleBootstrap_cpp

Both will connect to OOo instead.
This is true in the case the user uses the helper classes available in LibO
SDK.
For details how all this is supposed to work, the same pages of the OOo
DevGuide recalled above are explanatory.

The Java and C++ bindings have two functions that use the symlink
/usr/bin/soffice in order to reach the actual LibO installation.
So /usr/bin/libreoffice should be symlinked to
/opt/libreoffice/program/soffice, or more generally to <install
dir>/program/soffice

The soffice and soffice.bin inside ../program must stay named as now, because
they can be used as target for autostart of LibO.

There is mail already exchanged on the topic, in which I'm afraid I didn't
explain the problem in details:

http://lists.freedesktop.org/archives/libreoffice/2010-October/000416.html
http://lists.freedesktop.org/archives/libreoffice/2010-October/001031.html

Some matter may still be open; ATM I don't know the way python and CLI bindings
work; I'm not sure they require the same changes.

A quick and easy way to see the behavior described here is to try with testtool
in universal LibO:

To reproduce (test carried out with a build from a pull -r done on Oct,20th
around 2 pm):
1) install universal LibO, it will show up in /opt/libreoffice.
2) following the steps here:
http://wiki.documentfoundation.org/Qa/testing/Using_Testtool
prepare the testtool environment and start the test as instructed
3) Oracle OOo is started instead of LibO.

Solutions to the symlink issue: I see two possible:

1) apply the patches I will attach, so the original behavior is restored;

2) leave the situation as it is, but documenting somewhere in the LibO DevGuide
how the features above are working (e.g. the need to always specify
the path on the start line); and if testtool will be needed for testing update
testtool code accordingly.

A test case can be built using Java, as an example, there is a Java program
here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/First_Contact

I modified and adapted it to check this issue, but I didn't attach it here
because I'm not sure of the license issues: the PDL for documentation,
does it fit the guidelines/bylaws here?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.