Issue Details (XML | Word | Printable)

Key: GLASSFISH-3994
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Tim Quinn
Reporter: Tim Quinn
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

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

Created: 10/Jan/08 02:10 PM   Updated: 06/Mar/12 10:05 PM
Component/s: standalone_client
Affects Version/s: v2.1
Fix Version/s: not determined

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,994
Status Whiteboard:

as911-na

Tags:
Participants: kumara, Tim Quinn, Tom Mueller and ymajoros


 Description  « Hide

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.



Tim Quinn added a comment - 10/Jan/08 02:16 PM

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.


Tim Quinn added a comment - 22/Sep/08 11:15 PM

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


ymajoros added a comment - 29/Oct/08 02:53 AM

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?


ymajoros added a comment - 29/Oct/08 02:53 AM

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?


kumara added a comment - 01/Sep/09 01:09 AM

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


Tom Mueller added a comment - 06/Mar/12 10:05 PM

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