Maybe the mechanism that sets properties after the VM is started but before the application is invoked, got broken with this Java update, or maybe this was an intentional but undocumented change. While "insecure" properties stopped working, we realized that "secure" properties would still be set correctly. The following properties, as well as properties beginning with either "javaws." or "jnlp.", are considered "secure" and will be passed to the VM in this way: Some properties are considered "secure" properties and can be passed as -Dkey=value arguments on the java invocation command line. Properties set in the jnlp file will normally be set by Java Web Start after the VM is started but before the application is invoked. The JNLP Spec gave a hint for a work-around: We experienced the same Problem with Java 7 Update 45 (1.7.0_45).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |