Subject | Re: Problems using FirebirdSQL-1.5.0BetaJDK_1.4 driver with JBoss 3.0.x |
---|---|
Author | Roman Rokytskyy |
Post date | 2004-01-26T15:16:24Z |
Hi,
solution to your problem, maybe others do...
Issue with JCA framework and JBoss support is that David Jencks (he
started JayBird project and was main developer here, and he developed
JCA support in JayBird as well as in JBoss) does not participate
actively here lately. Also, as far as I know, he left JBoss project,
and I am not sure if you get support for Firebird in JBoss forums. Try
to contact him through Core Developers Network, that's where you
should be able to find him.
Seems that you have following options:
- get support from David Jencks;
- do not use JCA framework, but either java.sql.Driver or
javax.sql.DataSource, or javax.sql.ConnectionPoolDataSource
interfaces. You loose correct work in distributed tx environment, but
if your DB is the only tx-enables resource, no problem there;
- upgrade to 3.2.x
Hope this helps you.
Best regards,
Roman Rokytskyy
> A little sad that nobody seems to pay attention to this issue. Well,Sorry that I answer too late for you... Unfortunately I do not have
> just got to stick with MySQL until somebody comes up with a solution
> or we are ready to port our application to JBoss 3.2.x.
solution to your problem, maybe others do...
Issue with JCA framework and JBoss support is that David Jencks (he
started JayBird project and was main developer here, and he developed
JCA support in JayBird as well as in JBoss) does not participate
actively here lately. Also, as far as I know, he left JBoss project,
and I am not sure if you get support for Firebird in JBoss forums. Try
to contact him through Core Developers Network, that's where you
should be able to find him.
Seems that you have following options:
- get support from David Jencks;
- do not use JCA framework, but either java.sql.Driver or
javax.sql.DataSource, or javax.sql.ConnectionPoolDataSource
interfaces. You loose correct work in distributed tx environment, but
if your DB is the only tx-enables resource, no problem there;
- upgrade to 3.2.x
Hope this helps you.
Best regards,
Roman Rokytskyy