
A note about verifyJarfile.js
------------------------------
Say you have a web page that detects Java, that uses the following:
var status = PluginDetect.isMinVersion('Java', '0', 'getJavaInfo2.jar');

Imagine that PluginDetect is able to successfully detect Java in your web page on the particular
browser that you are using. BUT, it does so without needing to start up the Java Runtime Environment.
In this particular case, PluginDetect had no need to use the 'getJavaInfo2.jar' input argument
that we specified above. So we really don't know for sure whether that input argument has
the correct path and spelling, despite Java being successfully detected.

Alot of people seem to forget that a jarfile's path is relative to the webpage, NOT relative
to the external javascript file. If jarfile='jetJavaInfo2.jar', then this implies that the jarfile
is in the same folder as the web page. It does not matter if you are using an external javascript
code that is located in a different folder.

For this reason, it would be nice to make sure that the jarfile path/name was correctly specified.
To verify your jarfile name/path in a Java detection webpage you are designing,
you can use the verifyJarfile.js script. Instructions on how to use verifyJarfile are located
in the verifyJarfile.js file itself.


