Throwing C++ exception in JNI

[Boris Tabenkin]

I am wondering of anyone knows the answer to the following. I have a C++
library that is loaded in the VM by JNI. The library throws C++ exceptions.
This work fine on Windows, but on Solaris there are problems. This was
related to the fact that the C++ runtime was not initialized by the JVM
since the JVM is written in C. Does anyone know if this has been fixed in
more recent JVMs or is there some sort of a compiler trick that can be
applied to force the proper initialization to occur when the JVM starts up.

[Gordon Beaton]

On Tue, 07 Sep 2004 13:13:50 GMT, Boris Tabenkin wrote:

I am wondering of anyone knows the answer to the following. I have a
C++ library that is loaded in the VM by JNI. The library throws C++
exceptions. This work fine on Windows, but on Solaris there are
problems. This was related to the fact that the C++ runtime was not
initialized by the JVM since the JVM is written in C.

Why don't you do the necessary initialization in JNI_OnLoad()?

/gordon

--
[ do not email me copies of your followups ]
g o r d o n + n e w s @ b a l d e r 1 3 . s e

[Joe Blow]

Gordon Beaton wrote:

On Tue, 07 Sep 2004 13:13:50 GMT, Boris Tabenkin wrote:

I am wondering of anyone knows the answer to the following. I have a
C++ library that is loaded in the VM by JNI. The library throws C++
exceptions. This work fine on Windows, but on Solaris there are
problems. This was related to the fact that the C++ runtime was not
initialized by the JVM since the JVM is written in C.

Why don't you do the necessary initialization in JNI_OnLoad()?

/gordon

I am confused, is this a function that I implement in my own DLL? How
does that get called since the JNI code doesn't happen till something
happens in Java. The C++ runtime is something that is typically
initialized by the JVM runner, not a client dll.

[Joe Blow]

Gordon Beaton wrote:

On Tue, 07 Sep 2004 13:13:50 GMT, Boris Tabenkin wrote:

I am wondering of anyone knows the answer to the following. I have a
C++ library that is loaded in the VM by JNI. The library throws C++
exceptions. This work fine on Windows, but on Solaris there are
problems. This was related to the fact that the C++ runtime was not
initialized by the JVM since the JVM is written in C.

Why don't you do the necessary initialization in JNI_OnLoad()?

/gordon

I am confused, is this a function that I implement in my own DLL? How
does that get called since the JNI code doesn't happen till something
happens in Java. The C++ runtime is something that is typically
initialized by the JVM runner, not a client dll.

[Gordon Beaton]

On Wed, 08 Sep 2004 12:27:18 GMT, Joe Blow wrote:

Gordon Beaton wrote:

Why don't you do the necessary initialization in JNI_OnLoad()?

I am confused, is this a function that I implement in my own DLL? How
does that get called since the JNI code doesn't happen till something
happens in Java. The C++ runtime is something that is typically
initialized by the JVM runner, not a client dll.

Is it not possible to do the necessary initialization manually?

You implement JNI_OnLoad() in your DLL, and the JVM will invoke it
when it loads the library.

I can't see how the the fact that the JVM was written in C should make
any difference here. It is normally possible to link C and C++ object
files without any problems.

I am a C (not C++) programmer, and don't know how the C++ runtime is
normally initialized, so maybe I just don't fully understand the
problem.

/gordon

--
[ do not email me copies of your followups ]
g o r d o n + n e w s @ b a l d e r 1 3 . s e