With JNLP on 1.4.2 and 1.5.0, I have become accustomed to being able to locate the Jar files that we distribute as our application. With the most current snapshot of 1.6.0, the entire directory structure is dramatically changed.
In going through as much of the source code as I think might be relevent, I come to the conclusion that I was never aware of JWS cache behavior -- so you could conclude that I was just dumb lucky in developing a JarFileHelper class that allowed critical functionality. Evidently at some point in time between 2001 and 2005, at least conceptually, it was possible for the user to determine whether it would be 'deal or no deal', i.e., 'cache or don't cache', but I never made any such setting in successfully working with the downloaded content in the past two major releases.
Two questions, then:
01. Is there any mechanism in Mustang for the user to control whether the downloaded Jar files will be cached or not cached? [I am using the terms as if they really mean -- will the JNLP-downloaded Jar files be stored some in special, internal format, or will they be stored in the host file system as ordinary files with the customary layout?]
02. If not, is there some public api for extracting individual file content from the JNLP-downloaded Jar files when they are stored in that internally cached format?