On 19 Nov 2014 07:57:21 -0800, "hugo.larson@... [Firebird-Java]"
<Firebird-Java@yahoogroups.com> wrote:

> A remark. I'm using ISO8859_1 already in my application.
> If the encoding is missing the a "UnsupportedEncodingException" should

be

> thrown but it's not.
>
> So the encoding is there by default but for some reason JayBird does not
> find it or thinks it's Japanese with Exselsior JVM.

The problem is not with you using ISO8859_1 (nor is Jaybird trying to load
a Japanese character set instead). On first access to the EncodingFactory,
Jaybird initializes a collection with **all** encodings from the
isc_encodings.properties file. In Jaybird 2.2.1 I added support to use all
Java aliases for a character set (instead of only the Java character set
name defined in isc_encoding.properties). The error occurs when Jaybird
tries to obtain those aliases and the character set (in this case EUC_JP)
doesn't exist.

This didn't happen before, because when you use NONE the EncodingFactory
is - usually - not used, and therefor no mapping from Firebird to Java
character sets (and vice versa) is loaded.

Mark