Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible

[Tobias Krais <tuxmail-spam@bats.ch>]

Hi Rene and also api.openoffice.org-list,

short description for the API list (esp. Jürgen Schmid): in February you
told me how to use the class loaders for bootstraping OO. You will
remember it looking at this code snippet:
http://codesnippets.services.openoffice.org/Office/Office.BootstrapOpenOffice.snip

Now I reportet a Debian because linking the soffice executable solves
the problem. We ask for your opinion.

>>>> Solutions:
>>>> - add a link /usr/bin/soffice to /usr/lib/openoffice/program/soffice
>>>> - don't add additional functionality to /usr/bin/ooffice and replace it
>>>> with a link in first solution.
>>> Would symlinking soffice to the current ooffice work, too?
>> No.
>>
>> Please see following link:
>> http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14792
>>
>> after adding the link to the soffice executable it worked out, altough I
>>  told in the link above it didn't work.
> 
> There's no soffice executable, that's why I asked. soffice is a sh script 
> calling soffice.bin. Which is similar to ooffice as perl script calling 
> soffice. (Or, if we change to ooqstart-invocation completely in the future, 
> just a sh script calling ooqstart (C-Program) calling soffice)
> 
> If only the link to /usr/lib/openoffice/program/soffice makes sense. DAMN.
> 
> Because a soffice binary might encourage normal users to run that instead of
> the oo*.
> 
> Do you know exactly under which circumnstances it works and with which not?

Not more as I did up to now. Removing the link from /usr/bin/soffice to
/usr/lib/openoffice/programm/soffice stops the class loaders from working.

API-List: What makes the soffice exec so special that it only works with
the soffice exec? Your help is appreciated.

Greetings, Tobias