db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: derbytools.jar loading derbyclient.jar
Date Mon, 27 Feb 2006 20:17:13 GMT
On 2/27/06, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:
> Andrew McIntyre wrote:
>
> >I hadn't considered the mixed jar environment, sorry, and I guess
> >there's no choice but to take out the Class-Path attribute from
> >derbytools.jar. Sadly, it cripples the spirit of 1019: there is then
> >no direct path to using the tools and one must explain classpath
> >before using the tools. Ah well, so it goes...
>
> Could it possibly only load it iff no other derbyclient.jar  is
> available?

Unfortunately, not with the facilities provided by the manifest.

BUT, since we've already got a class in front of the tools in
derbytools.jar, it could:

* check for the presence of the drivers by trying to load one
* if not present, try to locate derby.jar or derbyclient.jar in the
same location from which derbytools.jar was loaded
* if we find a jar in the same location as derbytools.jar, load the
driver classes from it

For now, I'll back out the Class-Path attribute on derbytools.jar and
if the above sounds reasonable I'll look into what it would take to do
that.

andrew

Mime
View raw message