A known issue was with putting the resources under either the default context or the global resources. If you do thins you end up with various errors. This might not be the same issue of course. To fix it place the resources in a Context you intend to run under.Unfortunately it's already in a specific context as far as I can tell :( I've downloaded the source to dbcp and it seems it's throwing a SQLException on DriverManager.getDriver(url) but there's no reason I can see that it should, as the url it returns worked just fine when we were doing it the old fashioned way, the only difference is we called getConnection instead of calling getdriver and doing things seperately like dbcp does. Anybody know why getDriver would throw a SQLException where getConnection would not?
This is really starting to get ridiculous, I've spent way too long trying to make this work, and I'm pulling my hair out so to speak.
Cheers, -Josh
-- [ Josh 'G' McDonald ][ 0415 784 825 ][ http://www.gfunk007.com/ ]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
