EncodingFactory doesn't handle UnsupportedCharsetException [JDBC371]

[firebird-issue-importer]

Submitted by: @mrotteveel

EncodingFactory in Jaybird 2.2 doesn't handle UnsupportedCharsetException (and IllegalCharsetNameException).

As reported in Firebird-java:

Hi Mark,

I get this exception when setting the character set as advised with Excelsion JET jvm.
Tried with both WIN1252 and ISO8859_1.

BR,
Hugo.

java.nio.charset.UnsupportedCharsetException: EUC_JP
at java.nio.charset.Charset.<unknown>(Unknown Source)
at org.firebirdsql.encodings.EncodingFactory.loadEncodings(Unknown Source)
at org.firebirdsql.encodings.EncodingFactory.getJavaEncoding(Unknown Source)
at org.firebirdsql.jdbc.FBDriverPropertyManager.<unknown>(Unknown Source)
at org.firebirdsql.jdbc.FBDriverPropertyManager.normalize(Unknown Source)
at org.firebirdsql.jdbc.AbstractDriver.connect(Unknown Source)

Commits: 649a0fc FirebirdSQL/fbt-repository@f189d96

[firebird-issue-importer]

Commented by: @mrotteveel

The new EncodingSet in Jaybird 3 already handles this; only needs to be fixed in Jaybird 2.2.

[firebird-issue-importer]

Modified by: @mrotteveel

Fix Version: Jaybird 2.2.6 [ 10588 ]

[firebird-issue-importer]

Commented by: @mrotteveel

Now catching IllegalCharsetNameException and UnsupportedCharsetException, tested by misspelling the character set name in isc_encodings.properties

[firebird-issue-importer]

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

[firebird-issue-importer]

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]