Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6394576

using associations with Single Instance causes extra security popup on second and later launches.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 6
    • 6
    • deploy
    • None
    • b77
    • generic
    • generic

      When using associations to launch Java Web Start, javaws is run with the args:
      "javaws -open <filename> <jnlp-filename>" or "javaws -print <filename> <jnlp-filename>"
      to prevent a security dialog from popuping up, the filename passed in is granted read and write permission (in the first case) and read permission (in the second case"
      But when using the SingleInstanceService, the native code is called with
      "javaws -open <filename> <jnlp-filename>" but the java code isn't called that way.
      As a result the code in Main that makes sure sandbox permissions include read (or read and write) permission to the given file is not ever read.
      We need to add code in SingleInstanceServiceimpl where the newActivation is called to insure that the required file permissions are granted.

            herrick Andy Herrick (Inactive)
            herrick Andy Herrick (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: