Re: [enhydra] Postgres driver kills MySQL communication

["Sinisa Milosevic" <sinisa@xxxxxxxxxxxxx>]

Hi Mike,

Yes it is possible to write Enhydra application using your scenario. But I
think without aim you want to attain. Enhydra 5.1.x doesn't work without
dods-runtime.jar. It must be in system classpath (with other Enhydra jars).
If you use DODS standalone, dods will be initialized somewhere in
application using different conf file, but Enhydra classloader first check
system classpath to find classes and uses always dods-runtime from system
classpath.
Separation DODS from Enhydra was done to enable DODS to be used in
non-enhydra application (swing, web...), not to exclude DODS from Enhydra.

In Enhydra 6,  EAF contains only Database Manager API of dods jars.
DatabaseManager implementations are not obligatory for Enhydra applications
which work without DODS.

Regards,
Sinisa


----- Original Message -----
From: "Michael Strapp" <mstrapp@xxxxxxxxxxxxx>
To: <enhydra@xxxxxxxxxxxxx>
Sent: Tuesday, November 02, 2004 9:11 PM
Subject: Re: [enhydra] Postgres driver kills MySQL communication


> Hi Sinisa,
>     OK, so Enhydra 5.1.x doesn't work without the dods-runtime.jar (as
Petr
> confirmed).  Is it possible to write an Enhydra app to, rather than using
> DODS through the multiserver (i.e. using the usual static methods such as
> getDatabaseManager() in the com.lutris.appserver.server.Enhydra class), to
> instead use "DODS standalone" (i.e. using static methods from some other
> class) with the database configuration from the app's .conf file moved
into
> some separate configuration file (the same configuration file that a
> non-Enhydra app would use)?
>
> Mike.
>
> ----- Original Message -----
> From: "Sinisa Milosevic" <sinisa@xxxxxxxxxxxxx>
> To: <enhydra@xxxxxxxxxxxxx>
> Sent: Tuesday, November 02, 2004 4:54 AM
> Subject: Re: [enhydra] Postgres driver kills MySQL communication
>
>
> ....
>
> Regarding DODS and Enhydra separation. DODS is standalone and it can work
> without Enhydra. But Enhydra 5.1.x can't work without dods-runtime.jar.
> Enhydra creates DatabaseManager in StandardApplication class. Because of
> that enhydra jars and dods-runtime.jar must be loaded by the same
> classloader.
>
> ....
>
>
>


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


>
> --
> 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
>