Subject | JDBC or JCA |
---|---|
Author | Juan Pedro López Sáez |
Post date | 2005-02-10T08:51:33Z |
Hello everybody.
I have a MDB driven application inside a JBoss container and need to
access a Firebird database without XA requirements.
Currently I'm using JBoss 4.0, Firebird 1.0.3 and Jaybird 1.0.1 on a
linux box.
AFAIK I have two choices:
- Use Jaybird as a normal JDBC driver.
- Use Jaybird as a JCA connector.
I don't really know what the main advantages/drawbacks of each option
are, but my first thought tells me to use Jaybird as a normal JDBC
driver because of some misfunctions detected on the other mode in
previous threads in this list. Is this a correct approach? Could I miss
any important feature if I avoid the JCA alternative?
Jaybird's FAQ shows how to use Jaybird in the JCA fashion but I'm not
sure how to use it on the other way. Could anybody give me some hints on
that direction?
Thank you very much.
Juan Pedro Lopez
I have a MDB driven application inside a JBoss container and need to
access a Firebird database without XA requirements.
Currently I'm using JBoss 4.0, Firebird 1.0.3 and Jaybird 1.0.1 on a
linux box.
AFAIK I have two choices:
- Use Jaybird as a normal JDBC driver.
- Use Jaybird as a JCA connector.
I don't really know what the main advantages/drawbacks of each option
are, but my first thought tells me to use Jaybird as a normal JDBC
driver because of some misfunctions detected on the other mode in
previous threads in this list. Is this a correct approach? Could I miss
any important feature if I avoid the JCA alternative?
Jaybird's FAQ shows how to use Jaybird in the JCA fashion but I'm not
sure how to use it on the other way. Could anybody give me some hints on
that direction?
Thank you very much.
Juan Pedro Lopez