dcsimg
CreateJavaVM fails if dlls are located in application directory
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Larry_Dawes
Posted On:   Tuesday, November 19, 2002 01:09 PM

I am using sun's j2re1.4.1_01 runtime dlls in conjunction with a C++ application that calls them using JNI. To prevent conflicts with with pre-existing jdk's on client machine, would like to include all java dlls in the application directory and not have to set the Path variable. When the awt.dll and jvm.dll are moved to the application directory, the create javavm call returns -1 and both jvm and env pointers remain null. (no problem if only the current jdk/sdk/jre is included in path) Is there a way to include the dlls in the application directory in such a way as to not require setting the path variable, thus eliminating conflict with any other jvm or jdk that the client may have installed    More>>

I am using sun's j2re1.4.1_01 runtime dlls in conjunction with a C++ application that calls them
using JNI.
To prevent conflicts with with pre-existing jdk's on client machine, would like to include all java
dlls in the application directory and not have to set the Path variable.
When the awt.dll and jvm.dll are moved to the application directory,
the create javavm call returns -1 and both jvm and env pointers remain null. (no problem if only
the current jdk/sdk/jre is included in path)
Is there a way to include the dlls in the application directory in such a way as to not require
setting the path variable, thus eliminating conflict with any other jvm or jdk that the client
may have installed and pointed to in the path?

   <<Less
About | Sitemap | Contact