-
Bug
-
Resolution: Fixed
-
P2
-
6u10, 6u15
-
b03
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2198803 | 7 | Calvin Cheung | P2 | Resolved | Fixed | b104 |
Use of jnlp.packEnabled and jnlp.versionEnabled should not cause any JVM relaunch.
Right now, if specified in JNLP file only, it will relaunch JVM, for both browser applet and webstart application case.
This property is only used by webstart/plugin to determine whether we should reqest .jar.pack.gz instead of .jar for JAR download.
So as long as we set it right after we parse the JNLP file, we are good. There is no reason to relaunch JVM because of this.
Right now, if specified in JNLP file only, it will relaunch JVM, for both browser applet and webstart application case.
This property is only used by webstart/plugin to determine whether we should reqest .jar.pack.gz instead of .jar for JAR download.
So as long as we set it right after we parse the JNLP file, we are good. There is no reason to relaunch JVM because of this.
- backported by
-
JDK-2198803 jnlp.packEnabled and jnlp.versionEnabled should not cause any JVM relaunch
-
- Resolved
-
- duplicates
-
-
- Closed
-
- relates to
-
JDK-6797730 Umbrella: Applet startup performance improvements
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-