From: "Jeff Crump" <###@###.###>
Subject: JNI and 1.2 directory layout
To: <###@###.###>
Date: Wed, 24 Mar 1999 18:57:03 -0600

Our application uses JNI to "embed" a JVM in a server product. All was fine
with JDK 1.1.x, but 1.2 poses a problem: jvm.dll isn't on the path! It's in
the 'classic' directory under the jre/bin directory (Win/NT here). Not a
real problem, although we we really don't want to mess with the application
path.

The real problem is what Sun has chosen to do next. From the JVM sources, I
see that it follows this algorithm to locate the VM native libraries
(java.dll and others):

     - Go up two levels of directory structure
     - Go down to a 'bin' directory

So now I need to change the app path AND have a directory layout which is at
least three levels deep.

The direction I've chosen, however, is to create a DLL which is statically
linked to the JRE but is itself dynamically loaded.

I can (sort of) understand the 'cleanliness' argument that's proffered in
the documentation, in that different VM implementations live in different
directories. But these kind of requirements make life very difficult,
especially for embedded VM deployment. Thanks a lot, Sun.

Has anyone else dealt with this problem?

jeff

-----------------------

Jeff Crump
Object Design, Inc.
###@###.###


Unsubscription, archives, FAQ - http://www.xcf.berkeley.edu/lists.html