Thank you so much for the responses.

So using Jaybird as a JCA connector is a safe matter.

What about the XA capabilities? An open issue in the wiki is "Fix the
issues with XA protocol in JCA code".

In case in need distributed transactions inside a J2EE server, what is
the best choice? Should I take care of something to prevent troubles?

Thank you very much

Juan Pedro Lopez

> Hi,
>
> > Currently I'm using JBoss 4.0, Firebird 1.0.3 and Jaybird 1.0.1 on a
> > linux box.
>
> You can upgrade to JayBird 1.5.5, it will also work with Firebird 1.0.3.
>
> > - 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?
>
> The only thing you miss is distributed transactions. However, in JCA mode
> the only known (did I forget something) issue is that JayBird incorrectly
> returns list of transactions "in limbo" (in other words, transactions that
> were prepared but not committed).
>
> > 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?
>
> Just take any example from JBoss, for example HSQLDB one, change the name of
> the driver and other params and go-go-go. :)
>
> Roman
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

--
Juan Pedro López Sáez
ALTIRIA TIC, Soluciones en Servicios Móviles
Tlf: 913 311 198
Móvil: 610 258 837
www.altiria.com