I am developing a Java program in eclipse using a proprietary API and it throws the following exception at run-time:
java.io.UnsupportedEncodingException:
at java.lang.StringCoding.encode(StringCoding.java:287)
at java.lang.String.getBytes(String.java:954)...
my code:
private static String SERVER = "localhost";
private static int PORT = 80;
private static String DFT="";
private static String USER = "xx";
private static String pwd = "xx";
public static void main(String[] args) {
LLValue entInfo = new LLValue();
LLSession session = new LLSession(SERVER, PORT, DFT, USER, pwd);
try {
LAPI_DOCUMENTS doc = new LAPI_DOCUMENTS(session);
doc.AccessPersonalWS(entInfo);
} catch (Exception e) {
e.printStackTrace();
}
}
The session appears to open with no errors, but the encoding exception is thrown at doc.AccessEnterpriseWS(entInfo)
Through researching this error I have tried using the -encoding option of the compiler, changing the encoding of my editor, etc.
My questions are:
- how can I find out the encoding of the .class files I am trying to use?
- should I be matching the encoding of my new program to the encoding of the API?
- If java is machine independent why isn’t there standard encoding?
I have read this stack trace and this guide already —
Any suggestions will be appreciated!
Cheers
Run it in your debugger with a breakpoint on
String.getBytes()orStringCoding.encode(). Both are classes in the JDK so you have access to them and should be able to see what the third party is passing in.The character encoding is used to specify how to interpret the raw binary. The default encoding on English Windows systems in CP1252. Other languages and systems may use different a different default encoding. As a quick test, you might try specifying UTF-8 to see if the problem magically disappears.
As noted in this question, the JVM uses the default encoding of the OS, although you can override this default.
Without knowing more about the third party API you are trying to use, it’s hard to say what encoding they might be using. Unfortunately from looking at the implementation of
StringCoding.encode()it appears there are a couple different ways you could get anUnsupportedEncodingException. Stepping through with a debugger should help narrow things down.