glassfish
  1. glassfish
  2. GLASSFISH-3994

Java Web Start launch of app client fails if cache path contains a national character

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: v2.1
    • Fix Version/s: not determined
    • Component/s: standalone_client
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      3,994
    • Status Whiteboard:
      Hide

      as911-na

      Show
      as911-na

      Description

      As reported in this forum thread

      http://forums.java.net/jive/thread.jspa?threadID=35115&tstart=0

      launching an app client using Java Web Start fails if the Java Web Start cache
      path contains a national character - that is, one that must be encoded in a URL.

      In the particular case of the forum thread, the failure occurs on a Czech
      Windows XP system with the locale set to Czech.

        Activity

        Tim Quinn created issue -
        Hide
        Tim Quinn added a comment -

        The problem seems to be with the encoding (or lack thereof) in the downloaded
        JAR file name's path and to ensure that the correct GlassFish JARs run with the
        correct permissions (by dynamically modifying the security policy using the
        JARs' locations.)

        The GlassFish Java Web Start-aware app client container (ACC) explicitly locates
        the downloaded JARs so it can construct its own class loader with them in the
        class path. The URL which ClassPathManager.locateJARs constructs contains
        encoded spaces (as %20) but not encoded national characters. This causes
        permission failures because the generated policy information refers to URLs that
        are illegally formed - they contain the unencoded national character.

        An effective, if annoying, workaround, is to use the Java Control Panel to
        change the location of downloaded files so its path does not include a national
        character.

        Show
        Tim Quinn added a comment - The problem seems to be with the encoding (or lack thereof) in the downloaded JAR file name's path and to ensure that the correct GlassFish JARs run with the correct permissions (by dynamically modifying the security policy using the JARs' locations.) The GlassFish Java Web Start-aware app client container (ACC) explicitly locates the downloaded JARs so it can construct its own class loader with them in the class path. The URL which ClassPathManager.locateJARs constructs contains encoded spaces (as %20) but not encoded national characters. This causes permission failures because the generated policy information refers to URLs that are illegally formed - they contain the unencoded national character. An effective, if annoying, workaround, is to use the Java Control Panel to change the location of downloaded files so its path does not include a national character.
        Hide
        Tim Quinn added a comment -

        Marking as n/a for 9.1.1 - does not meet criteria

        Show
        Tim Quinn added a comment - Marking as n/a for 9.1.1 - does not meet criteria
        Hide
        ymajoros added a comment -

        Well, this stops glassfish application client from working on some computers!
        Encoding the url correctly doesn't look that complicated, is it? There is a 100%
        failure rate on some machine.

        Would it be possible to solve this?

        Show
        ymajoros added a comment - Well, this stops glassfish application client from working on some computers! Encoding the url correctly doesn't look that complicated, is it? There is a 100% failure rate on some machine. Would it be possible to solve this?
        Hide
        ymajoros added a comment -

        Well, this stops glassfish application client from working on some computers!
        Encoding the url correctly doesn't look that complicated, is it? There is a 100%
        failure rate on some machine.

        Would it be possible to raise the priority of this bug?

        Show
        ymajoros added a comment - Well, this stops glassfish application client from working on some computers! Encoding the url correctly doesn't look that complicated, is it? There is a 100% failure rate on some machine. Would it be possible to raise the priority of this bug?
        Hide
        kumara added a comment -

        Changing version from 9.1.1 to v2.1 to reflect new name/version.

        Show
        kumara added a comment - Changing version from 9.1.1 to v2.1 to reflect new name/version.
        kenaiadmin made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 3994 35598
        Hide
        Tom Mueller added a comment -

        Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.

        Show
        Tom Mueller added a comment - Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.
        Tom Mueller made changes -
        Fix Version/s not determined [ 11149 ]
        Fix Version/s 9.1.1 [ 10973 ]

          People

          • Assignee:
            Tim Quinn
            Reporter:
            Tim Quinn
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: