Issue Details (XML | Word | Printable)

Key: JDBC-371
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

EncodingFactory doesn't handle UnsupportedCharsetException

Created: 13/Nov/14 06:17 PM   Updated: 30/Dec/14 12:01 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.2, Jaybird 2.2.1, Jaybird 2.2.2, Jaybird 2.2.3, Jaybird 2.2.4, Jaybird 2.2.5
Fix Version/s: Jaybird 2.2.6

 Description  « Hide
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.


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)

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 13/Nov/14 06:19 PM
The new EncodingSet in Jaybird 3 already handles this; only needs to be fixed in Jaybird 2.2.

Mark Rotteveel added a comment - 18/Nov/14 08:33 PM
Now catching IllegalCharsetNameException and UnsupportedCharsetException, tested by misspelling the character set name in