Hi,
To follow established expectations on the various platforms, and, in
some cases, due to technical necessities of the various platforms. In
principle, on all platforms there are three layers (URE, Basis, Brand)
at potentially arbitrary positions (even relative to each other).
Within the URE layer, one difference among platforms is that Windows
has both executables and libraries in bin, while Unix has libraries in
lib. Another difference is that, since recently, Windows shifted
virtually all libraries from the Basis program to the Brand program
directory.
Thanks for the info on that.
OOoBean tries to connect to soffice via a named pipe, which requires
native code in libjpipe.so being called from jurt.jar. I assume that
some Java error occurs failing to load that native lib which would be
swallowed by the "catch ( java.lang.Throwable aExc )" at OOoBean.java
l. 184. I suggest you patch OOoBean.java to include
"aExc.printStackTrace();" before "throw new NoConnectionException();"
to give more information.
I patched OOoBean.java (and to a minor extent PipeConnection.java) and
it seems you were right on this one. It's failing at the method
createJNI(String) with "xxx_25B7Office" as parameter.
After looking deeper into the subject I decided to test if my
referencing to jurt.jar and the others.
Indeed there was the problem.
Since the folder structure under Linux and Windows were different I
decided to fix it with symbolic links. It works fine for all loading
jars, but seems to cause trouble if a jar needs JNI functions.
I referenced with a new manifest file to the original locations instead
of symbolic links and it works just fine :)
Don't know why symbolic links can not be used since they are referring
to the same node but anyway. It works, and that's what counts for the
customers ;)
Thank you for pointing me to the right direction Stephan and if you know
why exactly it's not functioning with links I would like to know that :)
Regards,
Steffen B
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
