-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
b03
-
generic
-
generic
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2200072 | 7 | Igor Nekrestyanov | P3 | Resolved | Fixed | b64 |
In the ideal situation webstart startup logic should behave as follows:
If all of the following is true:
a) initial JNLP file is local (even if it is in browser cache yet)
b) all required JNLP files contain <update check="background">
c) all required resources are present in the cache
Then startup of webstart application should not require any network requests.
Background thread should check for updates and install updates to the cache.
If all of the following is true:
a) initial JNLP file is local (even if it is in browser cache yet)
b) all required JNLP files contain <update check="background">
c) all required resources are present in the cache
Then startup of webstart application should not require any network requests.
Background thread should check for updates and install updates to the cache.
- backported by
-
JDK-2200072 Avoid network requests if everything is cached and JNLP has <update check="background">
-
- Resolved
-
- relates to
-
JDK-6838214 launch from desktop shortcuts of java web start application will not pick up JNLP update from server
-
- Closed
-