Reputation: 483
My software has it's own java, using which I have to run my application via jnlp
through javaws
. The application requires a certificate which is already imported in it's java. My script-file which is performing the javaws
call has the following codes:
set JAVA_HOME=C:\my_prog\client\java\jre
set PATH=C:\my_prog\client;%JAVA_HOME%\bin
start C:\my_prog\client\java\jre\bin\javaws -J-Djavax.net.ssl.trustStore=C:/my_prog/client/java/jre/lib/security/cacerts -verbose -wait http://localhost:8090/backend/MYClient.jnlp
The paths are set to make sure that the javaws
starts only with the specified java.
The popup from -verbose
argument shows that javaws
is starting with the given java and certificate. But when my client starts via JNLP, the clients log is showing System property java.home
as my Windows local java. As a result, it is failing to validate correct certification when required.
The java control panel
java settings also shows that it is in the list:
is there any properties file that the jnlp uses/reads for getting the java path for starting the application? Or is there any way to specify the java.home in the JNLP so that it starts only with the specific java?
Upvotes: 0
Views: 3657
Reputation: 117
Try using href attribute of j2se tag..
<resources>
<!-- Application Resources -->
<j2se version="1.6+" href=
"some location"/>
</resources>
Not sure of this though!
Upvotes: 1