Re: [enhydra] Postgres driver kills MySQL communication

["Michael Strapp" <mstrapp@xxxxxxxxxxxxx>]

Hi Petr,
   You can leave the database driver in the system classpath - from looking 
in my <enhydra-home>/dods/lib directory, it looks like the jar(s) I was 
referring to would be the dods.jar and/or dods-runtime.jar.  I don't think 
there are any other jars that contain DODS-related classes which the 
multiserver would use.  Moving those to the Server.ClassPath[] setting was 
what I was suggesting.

Mike.

----- Original Message ----- 
From: "Petr Stehlik" <pstehlik@xxxxxxxxxx>
To: <enhydra@xxxxxxxxxxxxx>
Sent: Monday, October 25, 2004 2:32 PM
Subject: RE: [enhydra] Postgres driver kills MySQL communication


V Po, 25. 10. 2004 v 20:24, Michael Warne píše:
> Hi Petr,
>
> I think Michael may be right.  Dods probably has static fields in the 
> class.  Once a java classloader loads a class, it is global to all other 
> classes loaded by the same classloader.
>
> I have had similar issues in the past, and I ended up running 2
> instances of Multiserver.  If you try Michaels suggestion let us
> know.  I have always had trouble trying to figure out when I should
> put a class in the Server.ClassPath[] of an application

AFAIK no database driver works when put in Server.ClassPath[] of an
application. What a pity.

Petr






--------------------------------------------------------------------------------


> --
> You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx 
> mailing list.
> To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws