> I have an analogous case, in which I have a single API for database > access, with choice of database (Oracle, MySQL,...) made at run-time. > The problem was simply solved using the 'Abstract Factory' pattern. This > means that I have two packages (....db.MySql, & ....db.Oracle), which > both include an implementation of a DBFactory. I then use ClassForName() > to load the appropriate implementation, and then call factory methods to > instantiate the appropriate classes.
But I need to bother with class loaders. The classes have the same name but different implementations. This resides outside of my control. Solution (in the standalone app) is to load the implementations on demand using different URLClassLoaders. /O -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
