OOo 3.0 process on Windows cannot be started using soffice.bin about jodconverter HOT 10 CLOSED

The simple fix is to invoke soffice.exe rather than soffice.bin.

But this means that from Java we have a reference to the wrapper process rather 
than
the real one, so e.g. killing the process when it's stuck may kill only the 
wrapper.

We need a better understanding of what this wrapper executable does.

The simple fix is to invoke soffice.exe rather than soffice.bin.

But this means that from Java we have a reference to the wrapper process rather 
than
the real one, so e.g. killing the process when it's stuck may kill only the 
wrapper.

We need a better understanding of what this wrapper executable does.

An interesting OOo issue: http://www.openoffice.org/issues/show_bug.cgi?id=62312

This explains why invoking soffice.bin in OOo 3.0 no longer works:
http://blogs.sun.com/GullFOSS/entry/ooo_3_est_omnis_divisa

So due to the new 3-layer OOo architecture

  http://wiki.services.openoffice.org/wiki/ODF_Toolkit/Efforts/Three-Layer_OOo

on Windows we need to add to the PATH "C:\Program Files\OpenOffice.org\Basis
3.0\program" and "C:\Program Files\OpenOffice.org\URE\bin" before being able to
invoke soffice.bin directly.

On Linux the OOo installation uses symlinks to find the Basis and URE paths. On
Windows - that doesn't have symlinks - there's a plain text file "C:\Program
Files\OpenOffice.org 3\basis-link" containing the path to Basis, and another 
plain
text file "C:\Program Files\OpenOffice.org\Basis 3.0\ure-link" containing the 
path to
URE.

After this treasure hunt we should be able to add the two paths to the PATH
environment variable before starting the process.

Fixed in r32 by appending the newly required paths to the environment before 
starting
the OOo process.

Great, thanks!