Karakun Support Forums

Thank you for your request.
We will take this into consideration when we do the next release planning.

If you are in need for this feature you can also consider sponsoring the development.

Setting the "ows.jvm.manager.cache.dir" in the response.var or in the deployment.properties file should work.

What currently is not supported is providing a list of pre-installed JVMs when doing an installation of OWS

We can reproduce the issue. Will get back to you once we have a fix.

I can confirm that by clicking the red buttons OWS is starting the java applications

I am not sure if I have understood everything. Here is a short description of what the code is doing: - get a vendor from the JNLP if allowFromJnlp is set to true and the vendor in the JNLP is different from '*' (any vendor) - if this did not lead to a vendor it will take the vendor specified in ows...

We are aware of this. Does it cause any problems for you?

Hello Nadine Thank you for your interest in OWS and also for reading the guide. We very much appreciate if someone takes the time to read what we provide. To your questions: If a property in the deployment.properties has default value it will not be saved. This is an optimization to make the file sm...

Can you please also provide us with the path of the directories where you have installed the JVMs

What you are describing sounds a lot like a source code bundle. This means it is the actual code written by humans and not a program ready to be executed in a Java Virtual Machine. Did you download the jemboss from this site: http://emboss.sourceforge.net/Jemboss/ ?? If yes please contact the author...

It looks like you are passing a JAR file to OpenWebStart instead of a JNLP file. OWS main args [-verbose, C:\Users\Leonardo\Downloads\jemboss.jar] In order for OWS to work correctly you need a JNLP file. Ask the provider of your application if they support Java Web Start and can provide you with a J...

Greate to hear that it is working. You should change your entry in the cache.json to read ' "managed": false '. This will tell OWS that the JDK was not downloaded by the JVM Manager. Main effect this flag has is that when a managed JVM is removed from the JVM Manager it is also physically deleted fr...

Did you see any improvements with the version 1.2.1 ??

I suspect, the formatting of the path to the cache dir may be incorrect.

@Janak
Can you test this on Windows and see if the path is resolved correctly using the above syntax

Most likely no, The reason for this is that OWS is a java launcher and as such it cannot know what the requirements of the next application to launch will be. Fixing it to a specific JVM instance may prevent some applications from working with OWS. Maybe you can give us the reason why you need a spe...

Also it is possible to host your own JVM download server.
see: https://github.com/karakun/OpenWebStart ... oad-server

We use install4j to build the installer and launcher for the java application. Because of license issues we cannot make this part open at the moment. You can use the Java from the github repository and build everything using maven. The main class is "PhaseTwoWebStartLauncher". Maybe you need to remo...

The information about the available JVMs is stored together with the cached JVMs. It is possible to set the system variable "XDG_CACHE_HOME" to a folder outside of the user home directory (e.g. "c:\ows-cache"). This will force all users to use the specified folder as their cache directory. As a cons...

If the above information did not help you then please provide the complete stage1 log file

Yes it works with most JNLP files.

OWS does not need any pre installed java.
Thus you should be able to remove all javas from your machine and still use OWS