Subject | Re: [Firebird-Java] UNICODE_FSS in JBoss |
---|---|
Author | Joachim Van der Auwera |
Post date | 2005-01-19T00:20:47Z |
Joachim Van der Auwera wrote:
It seems that patching the initializer in FBManagedConnectionFactory to read
public FBManagedConnectionFactory(GDSType type) {
this.type = type;
gds = GDSFactory.getGDSForType(type);
defaultCri = FBConnectionHelper.getDefaultCri(gds);
defaultCri.setProperty(ISCConstants.isc_dpb_lc_ctype,
"UNICODE_FSS" );
defaultCri.setProperty(ISCConstants.isc_dpb_local_encoding,
"UTF-8");
}
avoids the NPE. When setting the encoding another way, a
defaultCri.setProperty(xxx, null) seems to be inviked. Don't quite knwo how.
However, unfortunately, this still does not avoid the transliteration
errors.
Any clues?
Thanks for the help,
Joachim
> I am using JBoss 4.0.1 and have problems getting a unicode connection.As a followup, I have been investigating the cause of the problem.
It seems that patching the initializer in FBManagedConnectionFactory to read
public FBManagedConnectionFactory(GDSType type) {
this.type = type;
gds = GDSFactory.getGDSForType(type);
defaultCri = FBConnectionHelper.getDefaultCri(gds);
defaultCri.setProperty(ISCConstants.isc_dpb_lc_ctype,
"UNICODE_FSS" );
defaultCri.setProperty(ISCConstants.isc_dpb_local_encoding,
"UTF-8");
}
avoids the NPE. When setting the encoding another way, a
defaultCri.setProperty(xxx, null) seems to be inviked. Don't quite knwo how.
However, unfortunately, this still does not avoid the transliteration
errors.
Any clues?
Thanks for the help,
Joachim