Packaging DB2 jdbc driver with an application? Why not?

[pike]

I'm pushing the introduction of the DB2 "Universal" JDBC driver, to be
used in a type 4 architecture and thus negate the need for a DB2 client
installation on the (client) application server.

Because the related application would then have a built-in dependency
on the specific level of DB2 driver, each time the level of DB2
changes, then in theory the application has to be repackaged just to
change the driver.

Should the application be independent of the driver?

Opinions much appreciated.

[Mark A]

pike wrote:

I'm pushing the introduction of the DB2 "Universal" JDBC driver, to be
used in a type 4 architecture and thus negate the need for a DB2 client
installation on the (client) application server.

Because the related application would then have a built-in dependency
on the specific level of DB2 driver, each time the level of DB2
changes, then in theory the application has to be repackaged just to
change the driver.

Should the application be independent of the driver?

Opinions much appreciated.

You do not need to upgrade the client drivers (type 2 or type 4) each
time the DB2 server code is upgraded. At some point a client upgrade
may be desirable or necessary if the DB2 server is upgraded, but not
always.