-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jan Hlavat� wrote:
| We may have a problem with JDBC driver. | Or, more precisely, we don't have a JDBC driver for networked server | configuration of Derby ;( | http://incubator.apache.org/derby/manuals/getstart/gspr36.html states we | have to use JDBC driver | from IBM DB2, without providing exact pointers, or license information. | That was OK for IBM's Cloudscape, | but how about Derby? | | Can someone please explain the situation? I feel a bit funny about it... | | We need to know / find out: | | - Where the JDBC driver is (i guess its hidden inside DB2 distribution) | - Under what conditions it can be used (can we at all? Can we provide | it as a separate download?) | | If we can use the driver, we need a clear permission/license from IBM | for unlimited production | use and a separate download page for the JDBC driver for Derby users to | download from (or permission | to redistrubute on Derby site).
The DB2 JDBC Universal Driver will be available for free download and use from IBM's Developerworks. The Derby resources page will contain the link, currently it states the driver is only available by downloading the IBM Cloudscape 10 tech preview/beta.
http://incubator.apache.org/derby/derby_resources.html
The standalone download will have a licence that enables unlimited use by Derby users for connections to the Derby network server.
Note that the Derby resources page has some incorrect formatting that seem to show that RMIJDBC is a suitable driver for the network server. RMIJDBC is a separate network client/server model for JDBC, and is an alternative to Derby's network server.
Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBMJQeIv0S4qsbfuQRAlamAKCsil3F8Yhj1FSQFJx4RVYTjGUnMACeK1ur SN5bEH98+3U4hgMsj0/SXqE= =eprp -----END PGP SIGNATURE-----
