IMO most of the excessive complexity of the current driver comes from the
shenanigans necessary to have xa support.

Again IMO the principal selling point of firebird and this driver is that
it is as far as I know the only free open source driver/db with xa support.

Rather than creating 2 or more java drivers I'd rather see the effort put
into adding into firebird 2 the ability to do work on any transaction on
any (physical) connection.

Remember, among the goodies the jca support gives you essentially for free
is a DataSource with built in connection pooling.

david jencks

On 2002.05.20 22:11:15 -0400 David Warnock wrote:
> David,
>
> I am not yet fully sure of the result from what Blas is suggesting.
>
> But if it results in jdbc support being somewhat separated from the jca
> support then that is a big plus for anyone who like us is using the
> driver as a standard, basic, boring, traditional JDBC driver and are not
> using JCA (because our frameworks don't support it and neither do other
> drivers so why change).
>
> So I would support a refactoring that makes it simpler for people like
> me to follow where the strictly JDBC elements come from.
>
> I don't know if this repackaging will allow a JDBC driver without JCA
> support to be built, I have mixed feelings about that despite not using
> JCA at present.
>
> Thanks
>
> Dave
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>