On Sat, 16 Mar 2002 01:10, Miller, Mike P. wrote:
> We are having a problem with including the jdbc driver in with our sars.
> Basically the classloader avaliable to JdbcConnectionFactory cannot read
> the jdbc drivers' Driver class because it is in our application's lib
> directory. If we put the jdbc driver's jar in the phoenix/lib dir it
> will be available to all packages and the factory will be able to
> Class.forName the jdbc driver. Is there a better way to get around
> this? How do you make a resource included with one application
> avaliable to it's dependancies?
Unfortunately I don't know of a way around this at this stage. I believe all
jdbc drivers need to be in the ClassLoader of the calling code due to ugly
hacks in the DriverManager code. I can't think of any way around this at this
point of time.
--
Cheers,
Pete
"You know what a dumbshit the 'average man' on the street is? Well, by
definition, half of them are even dumber than that!"
J.R. "Bob" Dobbs
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
