Wrong permissions assigned to javaws.jar

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P1
    • 1.0.1
    • Affects Version/s: 1.0, 1.4.0
    • Component/s: deploy
    • None
    • 1.0.1
    • x86, sparc
    • solaris_7, windows_98
    • Verified

      Java Web Start v1.0 and v1.0.1 don't work with Merlin at all because of this
      problem. Java Web Start will not start up and hangs during startup. This appears to be because when a checkPermission is made where the call trace originated from a class in javaws.jar, javaws.jar is not given the correct set of permissions. So as a result Java Web Start appears to have very few permissions which aren't sufficient for it to start. It hangs attempting to read some startup .cfg file.

      We specify in our javaws.policy file:

      grant codeBase "file:{jnlpx.home}/javaws.jar" {
          permission java.security.AllPermission;
      };

      and invoke Java Web Start with 'java -Djava.security.policy=javaws.policy'.

      This works in Java 2 v1.2.2 and v1.3, but not in Merlin.

      More in comments....

            Assignee:
            Rene Schmidt (Inactive)
            Reporter:
            Steve Bohne (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: