Subject | Re: [IB-Java] Re: JDBC Type 4 Driver Status and final build for testing |
---|---|
Author | David Jencks |
Post date | 2001-10-27T03:30:24Z |
The modern standard for application servers to connect to enterprise
resources is jca. It provides clear, uniform, and comparatively well
explained interfaces between "drivers" (connectors in jca-speak) and
application servers and their connection pooling and transaction management
capabilities. We have the worlds first relational database driver that is
written from the ground up to support these jca interfaces and contracts
and provide jdbc/sql access to the underlying resource manager. I think
the future of database access in java is tied closely to j2ee and think we
should concentrate on providing the best support for application servers
that we can. I do not want to compromise or complicate this support in any
way. For instance, I would never have written the jdbc 1 Driver
implementations myself, as I regard them as horribly obsolete. However,
since the implementations Roman contributed did not interfere with the jca
architecture, I added them. They remain significantly less efficient than
using a standalone DataSource.
Note that you need the jta libraries anyway if your jdbc 2 driver supports
xa.
thanks
David Jencks
resources is jca. It provides clear, uniform, and comparatively well
explained interfaces between "drivers" (connectors in jca-speak) and
application servers and their connection pooling and transaction management
capabilities. We have the worlds first relational database driver that is
written from the ground up to support these jca interfaces and contracts
and provide jdbc/sql access to the underlying resource manager. I think
the future of database access in java is tied closely to j2ee and think we
should concentrate on providing the best support for application servers
that we can. I do not want to compromise or complicate this support in any
way. For instance, I would never have written the jdbc 1 Driver
implementations myself, as I regard them as horribly obsolete. However,
since the implementations Roman contributed did not interfere with the jca
architecture, I added them. They remain significantly less efficient than
using a standalone DataSource.
Note that you need the jta libraries anyway if your jdbc 2 driver supports
xa.
thanks
David Jencks
On 2001.10.26 21:41:06 -0400 kyle@... wrote:
> > No, J2EE is required. Unmanaged driver is the managed driver that
> > manages the transaction itself. :) All necessary .jar files should
> be
> > in CVS client-java/src/lib folder.
>
>
> I am not a JDBC expert, but I have used many different JDBC drivers.
> I have never heard of any of them having a dependency on J2EE
> libraries. I have also not heard this distinction between 'managed'
> and 'unmanaged' drivers... how does this relate to JDBC 1.0/2.0
> drivers, versus drivers enhanced for the JDBC 2.0 optional package
> (DataSources, etc.)?
>
> How difficult would it be to make this Firebird JDBC driver more
> standard, with no dependency on J2EE code, only on the core Java
> libraries and JDBC 2 Optional Package?
>
> Kyle Cordes
> www.kylecordes.com
>
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Java-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>