Roman,

> Looks fine, except that you use AppServerXADataSource, which I have
> implemented to cope with the issues in the Sun Application Server. You
> can try the
>
> org.firebirdsql.pool.FBConnectionPoolDataSource
>
> which also implements XADataSource interface. Also I am not sure with
> "Encoding" property when you change the class name - try setting
> "encoding" to "UTF8" or "charSet" to "UTF-8".

Oh, I see. After changing property DatabaseName to Database it seems to work. Thank you very much, Roman!

--Heiko

BTW, do you know something about the other (not working!?) way of defining a firebird datasource in jboss? The following is what comes with jboss 5 as an example for a firebird datasource definition:

<tx-connection-factory>
<jndi-name>FIrebirdDS</jndi-name>
<xa-transaction/>
<!-- uncomment to enable interleaving <interleaving/> -->

<rar-name>firebirdsql.rar</rar-name>
<connection-definition>javax.sql.DataSource</connection-definition>
<config-property name="Database" type="java.lang.String">localhost/3050:${jboss.server.data.dir}${/}fbtest.gdb</config-property>
<user-name>sysdba</user-name>
<password>masterkey</password>
<!--additional properties. only use one way of setting tx isolation, please
<config-property name="TransactionIsolation"></config-property>
<config-property name="TransactionIsolationName">TRANSACTION_READ_COMMITTED</config-property>
<config-property name="BlobBufferLength"></config-property>
<config-property name="Encoding">UNICODE_FSS</config-property>
-->
<min-pool-size>0</min-pool-size>
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
<!-- sql to call on an existing pooled connection when it is obtained from pool
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>Firebird</type-mapping>
</metadata>
</tx-connection-factory>