Karakun Support Forums

Thanks for the feedback. We will implement this feature in the next release planned for Nov end.

Also, an alternative solution could be to add a confirmation dialog "Do you really want to clean the OWS cache?" when the user inadvertently presses the "Purge" button in the "Launch Failure" dialog. Which solution do you prefer: hiding the "Purge" button through a property or a confirmation dialog?

Ok.

Then I guess you do not have a problem if you have to add this new property "ows.launcher.error-dialog.purge.enabled=false" to the deployment.properties on every user's machine when the new version of OWS is rolled out in your company.

Thanks for your request.

You are suggesting a property "ows.launcher.error-dialog.purge.enabled=false" to be specified in the deployment.properties file to suppress the "Purge" button in the Launch Error Dialog. This can be done. However, to understand your requirement better, may I ask you how ...

You can remove Java 25 from the JVM Manager list. Keep Java 8. Then in the "JVM Manager > Settings..." choose "Do not download any version". Then your Jnlp with specification "1.8+" will match the Java 8 in JVM manager and use it to run this Jnlp application.

For other Jnlp applications, it ...

Did you configure OWS to use Java 8 to run your application? What JRE version is specified in the Jnlp file?

Please send the OWS logs (refer to OWS Guide). However, this is a public forum so you have to be careful to mask sensitive data that you would not like others to see. You can consider buying ...

Your error occurs because javax.xml.ws (JAX‑WS) classes like HandlerResolver were removed from the JDK starting with Java 11. As can be seen in the screenshot OWS is downloading Java 21 to run your application. You need to configure OWS to use Java to run your application: https://openwebstart.com ...

We are happy to announce the release of OpenWebStart v1.14.0

https://github.com/karakun/OpenWebStart/releases

- OpenWebStart Team at Karakun

OWS does not work with Java 23+ : please see https://github.com/karakun/OpenWebStart/issues/621 .

With Java23, URLJarFileCallBack was removed and with Java 24 the SecurityManager has been removed. for the former a workaround implementation can be found but for the latter an option is to run OWS ...

Release 1.14.0 should happen by mid June.

I had a look at https://www.uscourts.cavc.gov/documents/Web_Start_Configure-Win10.pdf.

The applet does not run in a browser (Edge or Chrome). In the browser you can download the k2ajnlp.jsp which is associated with Oracle Java Web Start to run the applet as a stand alone Java application using ...

Your Jnlp file specifies that your Java application is an applet : <applet-desc...

OWS does not support applet. Browsers have stopped supporting Java plugin that would run applets.

You say the it is working with Oracle Java. In which browser are you running the applet?

I was able to run snyk test locally on OWS and ITW codebase and it has generated reports. Will try to fix the vulnerabilities.

@Janak - I have a similar concerns as John above. Based on my own experience, these seem to be consistent with the results I see for OpenWebStart using Snyk as the SAST. Would you be still be willing to verify and fix the findings, as offered above? Would love to have these issues resolved ...

We will include this in the next release, scheduled for the end of May,

1. So you were able to install OWS successfully.

2. Then you launched your Jnlp file with OWS.

3. OWS downloads resources and verifies the signing certificate and show the Security Dialog asking to trust the application.

4. You choose "Always Trust" and click on the Run button.

5. Your ...

Hi,

Just to clarify:

1. You installed OWS by running the installer OpenWebStart_windows-x64-x64_1_13_0.exe

2. Your are saying that during the last step of installation " it says that a page will open so it can be marked as trusted and so on"
I am not clear about this. The last screen of installer ...

Thanks for suggesting Snyk. We will verify and fix.

In addition to the VM arguments specified in the JNLP file, you can provide additional arguments through the environment variable JAVAWS_VM_ARGS. If any argument you add is not included in the list of valid VM arguments recognized by OWS, it must first be added to the JVM argument whitelist in the ...

You can pass a JVM argument to the JVM that starts the App specified in the Jnlp file in the following ways:

1. In the Jnlp file:


<<j2se version="1.8*" java-vm-args="-Dawt.useSystemAAFontSettings=lcd"/>


2. In the env var JAVAWS_VM_ARGS

3. You can specify JVM args for a particular Jnlp file ...