Potential problem with the forName is bad issue, we already have a method using forName:
convertClassNamesToClasses which turns a List of String into a List of Class using forName. So, a) this seems to be a problem? b) I'd like to point it at the new forName method (or however that gets solved). Hen On Tue, 1 Feb 2005 20:11:09 -0500, Henri Yandell <[EMAIL PROTECTED]> wrote: > On Wed, 2 Feb 2005 00:19:06 -0000, Stephen Colebourne > <[EMAIL PROTECTED]> wrote: > > I think that we would have to ask for classloader advice ;-) > > Probably. > > > I suspect we would need: > > > > loadClassSystemClassLoader() - Class.forName > > loadClassThreadContextClassLoader() - thread > > loadClassLangClassLoader() - from ClassUtils > > loadClass(ClassLoader) > > We could just do the latter? Let's all the options be used without us > having to drag through a list of all the likely options. No matter > what classloader advice we got, it's likely to be usable. > > Hen > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
