-
Enhancement
-
Resolution: Fixed
-
P2
-
6u10
-
b33
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2198359 | 7 | Andy Herrick | P2 | Resolved | Fixed | b64 |
Currently the new Java Plug-In can infer the codebase for JNLP-launched applets, allowing the developer to not specify it at all to maintain portability of their JNLP file and its associated resources. This is similar to functionality the JnlpDownloadServlet provides for Java Web Start applications with the $$codebase and other macros.
However, when such an applet is dragged out of the browser and relaunched from a desktop shortcut, the JNLP client does not know how to re-infer the original codebase. This means that any JNLP applet that the developer wants to drag out of the browser and relaunch from a desktop shortcut must have an absolute codebase, which is undesirable.
We should use the codebase, now stored in the LocalApplicationProperties with the fix for 6732975, to begin the re-launch process for such applets.
However, when such an applet is dragged out of the browser and relaunched from a desktop shortcut, the JNLP client does not know how to re-infer the original codebase. This means that any JNLP applet that the developer wants to drag out of the browser and relaunch from a desktop shortcut must have an absolute codebase, which is undesirable.
We should use the codebase, now stored in the LocalApplicationProperties with the fix for 6732975, to begin the re-launch process for such applets.
- backported by
-
JDK-2198359 DnD: should pick up codebase automatically for relaunches of dragged-out JNLP applets
-
- Resolved
-
- relates to
-
JDK-6761053 Desktop shortcuts for dragged applets from HTTPS servers do not relaunch and can not be customized
-
- Resolved
-