[GLASSFISH-3994] Java Web Start launch of app client fails if cache path contains a national character Created: 10/Jan/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: standalone_client
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Tim Quinn Assignee: Tim Quinn
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,994
Status Whiteboard:

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.



 Comments   
Comment by Tim Quinn [ 10/Jan/08 ]

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.

Comment by Tim Quinn [ 22/Sep/08 ]

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

Comment by ymajoros [ 29/Oct/08 ]

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?

Comment by ymajoros [ 29/Oct/08 ]

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?

Comment by kumara [ 01/Sep/09 ]

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

Comment by Tom Mueller [ 06/Mar/12 ]

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

Generated at Fri Aug 28 14:45:15 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.