The problem here is the jnlp file does not have an href.
If a jnlp application is launched normally (ie: by clicking on a jnlp file link in a browser) and it does not have an href to it's jnlp file, we cannot know where the jnlp file came from.
In that case we cannot match an ESL location or a location based DRS rule.
This is internally documented at: http://wiki.se.oracle.com/display/JPGC/Exception+Site+List
but does not seem to be documented in the release notes.
you can fix app by adding an href to the main jnlp file (in the jnlp file)
This solution will not work for customer since both jars and jnlp files are embedded in firmware.
we need a solution for subset of cases where Exception Site List can work in a jnlp application even when jnlp file has no href.
There is also a related problem that must be addresed, caused by ELS implementation..
When a jnlp application is run normally from a link, the jnlp file is downloaded to the browser and a copy is made in native code and its path is passed as main arg to com.sun.javaws.Main(). Now the code in XMLFormat and LaunchDesc consider that path the original location of the jnlp file, create a file URL to that path and set it as LaunchDesc._originalHref. (as if user has issued command "javaws <path>"). This is then passed to the constructor of the RuleId as the jnlpLocation, causing ESL and DRS to use this file URL as location. This is easy to fix since we know (via existing additional arg) when the jnlp file passed to main is a copy of one downloaded by browser)