I haven't investigated this problem personally but from discussions
with Joe I think that the problem is a bizarre "feature" of
DriverManager that attempts to protect you from yourself and instead
shoots you in the foot. I don't remember the exact details but
DriverManager won't supply Drivers for a URL unless they are in a
very specific classloader. I think this gets the client driver in a
classloader in which DriverManager will allow you to use it, whereas
in any other classloader you cant get to the client driver.
Sorry I'm kind of vague on the details -- I last ran into this
personally about 3 years ago.
thanks
david jencks
On Mar 8, 2007, at 11:32 PM, Lin Sun wrote:
Hi Joe,
Just curious...why would we want to have derbyclient as a system-
database's dependency? IIUC geronimo is using derby as embedded
system database, I don't see a need to add derbyclient as a
dependency.
Thanks, Lin
[EMAIL PROTECTED] wrote:
Author: jbohn
Date: Thu Mar 8 11:14:58 2007
New Revision: 516152
URL: http://svn.apache.org/viewvc?view=rev&rev=516152
Log:
add missing derby client jar to SystemDatabase
Modified:
geronimo/server/trunk/configs/system-database/pom.xml
Modified: geronimo/server/trunk/configs/system-database/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/configs/
system-database/pom.xml?view=diff&rev=516152&r1=516151&r2=516152
=====================================================================
=========
--- geronimo/server/trunk/configs/system-database/pom.xml (original)
+++ geronimo/server/trunk/configs/system-database/pom.xml Thu Mar
8 11:14:58 2007
@@ -72,6 +72,11 @@
</dependency>
<dependency>
+ <groupId>org.apache.derby</groupId>
+ <artifactId>derbyclient</artifactId>
+ </dependency>
+
+ <dependency>
<groupId>org.tranql</groupId>
<artifactId>tranql-connector-derby-embed-xa</artifactId>
<type>rar</type>
