Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think everyone gave good solid attempts at answering the problem. However, it turns out that I misdiagnosed the problem. </p> <p>I had a coworker take over the problem and asked him to get a JDK with debug flags on so we could debug the <code>JNLPClassLoader</code> to see what was going on as I had tried all of the suggestions here + some.</p> <p>We ended up getting OpenJDK because recompiling the JDK from scratch is a total nightmare (we tried). After getting OpenJDK working with our product and debugging through the <code>JNLPClassLoader</code> - it turns out that it was still using a REALLY old .jnlp from months earlier that had the resource path wrong and thus why it couldn't find the class.</p> <p>We were confused why it was still using the ancient .jnlp even though we had redeployed the server correctly many times with the correct .jnlp and lots of code changes between which were reflected in our client application when run.</p> <p>Well, it turns out that on client machines, Java caches the .jnlp file. Even if your application changes and it redownloads your application, it still won't re-download the new .jnlp for whatever reason. So it will use all of the new code, but look up resources/class paths using the cached .jnlp.</p> <p>If you run: <code>javaws -uninstall</code> On the client machine then that will clear the .jnlp cache and next time it will use the correct .jnlp file.</p> <p>Really sad that this was the problem. Hopefully, this saves someone else endless hours of frustration like it caused us.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload