PhilB wrote:When a vendor creates a complex application they need to attempt to verify that it does in fact work. And when customers claim that it failed then the vendor needs to figure out why and then attempt to fix it.
My question is: would the latest jre, JREv24 in my case, not be a "one JRE fits all"? An omnipresent runtime that candle handle all the java demands of my browser?
This is vastly complicated if one allows the user to use any and all versions of software associated with the application. Especiallys since when the application fails the users will often fail to tell the vendor that they are using some other version.
So the solution is to code it such that it will not even start unless only the version that it was certified with is in use.
jschell answered your question with a snicker and without any thought.
Check the page source for that forms app. You'll likely see the following line:
<PARAM NAME="TYPE" VALUE="application/x-java-applet;jpi-version=22.214.171.124">
"jpi-version" forces a particular version. It's functionality has been replaced with "version".
In the formsweb.cfg file on the server, replace "jpi-version" with "version", and everything will work as it should.
Although Oracle now owns Java, it seems they don't even read their own updates: