Thread: javaws issue - importing two jnlp files into system cache

Have an issue with deploying our application, which comes in two parts, with javaws

In our installer (which is coded in NSIS) we call javaws twice, each time referencing a different jnlp file. It looks like this:

 javaws -wait -shortcut -import -system http://192.168.1.82/launch?[params]

 javaws -wait -shortcut -import -system http://192.168.1.82/launch?[slightly different params]

Whichever jnlp file is second gets imported into System Applications. My guess is that it is overwriting the first imported application.

If anyone can shed light on how to fix this I would appreciate any help.

I'm not sure that your problem is clear. What needs fixing? Describe clearly what is happening and then what you'd like to happen.

Are you saying that

• you have 2 separately packaged parts of the application that are to be imported into the system cache,
• both of which have almost identical URL (to the respective jnlp files) except for the query string (the part after '?' in the URL), and
• it seems that only the 2nd jnlp file remains in the cache?

One way to test if the 2nd jnlp file is indeed overwriting the 1st is by executing the javaws commands manually via command line. Check the cache after each execution to see if the 1st jnlp file gets cached before being overwritten by the 2nd jnlp file.

If the 1st jnlp file is being overwritten, it might be that the 2 jnlp files are not uniquely identified. See Java Web Start - Frequently Asked Questions (FAQ) for the answer to the question, "How are Applications uniquely identified?"

I'm not sure... perhaps "Version-based Download Protocol" might also help in your case. See https://edelivery.oracle.com/otn-pub..._5-mr-spec.pdf (PDF file)