Thanks to Larry Sanderson at Sun for pointing me in the right direction:
j2sdkee1.2.1/config/default.properties (documented in
doc/release/ConfigGuide.html, guess I should have RTFM)
I've had a little better success since then (after fixing the case error in
the driver name). Unfortunately I still haven't managed to get a
functional system.
As per instructions, I added the db2 driver and datasource to the
properties file, thus:
jdbc.drivers=COM.cloudscape.core.RmiJdbcDriver:COM.ibm.db2.jdbc.app.DB2Driv
er
jdbc.datasources=jdbc/Cloudscape|jdbc:cloudscape:rmi:CloudscapeDB;create=tr
ue|jdbc/db2|jdbc:db2:<dbname>
DB2 has two jdbc drivers, COM.ibm.db2.jdbc.app.DB2Driver, used for
applications, and COM.ibm.db2.jdbc.net.DB2Driver, used for applets. I've
used a sample application that uses the application driver, so I know it
works. However, the JVM used by the j2ee server dies with a SIGSEGV (and
lots and lots of debug output) if I try to use the application driver with
EJB. If I try to use the applet driver, I end up with a
java.sql.SQLException: No suitable driver. The EJB server doesn't put out
any output at all, not even to the logs, for this.
I thought there might be an issue that the drivers are actually JDBC 2.0
and not 1.2 (or whatever the earlier "latest" was/is), but there doesn't
seem to be any support for JDBC 2.0 from DB2 for linux.
It's looking like noone else has tried using this combination so I may be
stuck (or more accurately I may simply have to use bean managed persistence
everywhere), but hopefully someone out there has an idea on how to proceed
they'd be willing to share...
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
