On Sun, 13 Jul 2003 18:23:07 -0700, Vladimir R. Bossicard wrote: >> Actually I think that the embeded could be a superset of the managed. >> The managed will not create the database for you, the embeded will. > > Or the managed and embed drivers are merged: a system property could for > example specify if the database should be created or not. You don't > write yet another class and let the embed driver be more flexible. > > When I say "system properties" I don't mean that everything should be > defined when the JVM starts up: you can store all infos in an xml file > and simply call System.setProperty in the base class of your program. > Sorry if this sounds elementary.
Not at all. There is potential for them to be merged. The embeded driver is the equivelant of the managed driver/managed server. The problem I have is the embeded driver doesn't seem to provide a clean method of shutting down the database. There's also much potential for merging configuration and establishment code from the xml-rpc driver. This should allow you to have local driver access and xml-rpc access. At the moment it looks as though the embeded driver will trounce the xml-rpc config for the database if they are in the same classloader scope. -k.
