FULL PRODUCT VERSION :

Java 1.7.0_60-ea Oracle Corporation JRE=1.7.0_60-ea-b02 JVM=24.60-b04 JWS=javaws-10.60.2.02

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]

A DESCRIPTION OF THE PROBLEM :
Accented characters as application arguments in supplied JNLP, when a signed JNLP is included in the main jar, are mis-read and translated into 7-bit ascii. This causes a failure in the launched application. This failure does not exist in Java 6.

If javaws.jar is directly executed on the JNLP with -J-Dfile.encoding=UTF-8, Java 7 will correctly launch it.

REGRESSION.  Last worked in version 6u45

ADDITIONAL REGRESSION INFORMATION:

Java 1.7.0_60-ea Oracle Corporation JRE=1.7.0_60-ea-b02 JVM=24.60-b04 JWS=javaws-10.60.2.02

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Have an application with a signed JNLP, and supply accented characters in the arguments of the launch JNLP, for example"??qu???". These will be incorrectly passed on to the application.

It appears that this happens with webstart relaunching itself.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Arguments are passed correctly.
ACTUAL -
Arguments are passed incorrectly, and translated into a different Charset.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
No messages from webstart.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Registry edit to include javaws argument "-J-Dfile.encoding=UTF-8" in the launch command.

This is essentially unacceptable for our user community.

SUPPORT :
YES