------- Additional Comments From [hidden email] 2005-06-02 08:12 -------
I'm opposed to attempting to load a specific adapter from the parent classpath
if one is found in the child classpath which doesn't work. If the user has the
lib in the child classpath, then:
* there's no guarantee it is the same version of the lib as in the parent, and
* the one in the parent will behave quite differently anyway, as it wont see
config files in the child etc.
I think this situation should be regarded as a *failed discovery*, which is
exactly what the existing code does. Invisibly failing over to the lib in the
parent could cause the user major confusion.