On 08/23/10 14:09, Rene Engelhard wrote:
On Mon, Aug 23, 2010 at 11:42:22AM +0200, Michael Stahl wrote:
i think i remember this error... it is caused by not finding some URE
dynamic libraries, like libjpipe.so.
the Java UNO bridge apparently uses native code via JNI for some things.
Then that is a bug in the bridge or the extension itself IMHO ...
on a Ubuntu box here the libraries seems to be in /usr/lib/ure/lib/libjpipe.so
so try adding "/usr/lib/ure/lib/" to CLASSPATH, see if that helps.
.. because ure-link is exactly what points to that /usr/lib/ure thing.
Anything which assumes that the ure is inside the OOo dir is wrong;
the only valid assumption is that *ure-link* is. That's how the three-layewr
OOo interface was defined.
The static
NativeLibraryLoader.loadLibrary(PipeConnection.class.getClassLoader(),
"jpipe"); in class com.sun.star.lib.connections.pip.PipeConnection
within jurt.jar effectively depends on finding a jpipe dynamic library
(libjpipe.so on Linux) through the Class-Path in the jurt.jar
META-INF/MANIFEST.MF, "ridl.jar unoloader.jar ../../lib/ ../bin/".
This works in standard OOo installations, where the jpipe dynamic
library is found relative to jurt.jar within the URE installation either
in ../../lib (Unix) or ../bin (Windows).
This fails if you either use a jurt.jar copied elsewhere, or the given
OOo installation does not preserve the above requirement.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
