JAX-WS like to look for non-existent classes. This costs something, by the time that ClassLoaderUtils.loadClass gets done making three (or is it four?) calls to the class loader. Are wrapper classes really legitimately possibly defined in all those different class loaders? Should I make a negative cache that recalls the nonexistence of classes once not found?
- Wrappers and non-existent classes and performance Benson Margulies
- Re: Wrappers and non-existent classes and performanc... Glen Mazza
- Re: Wrappers and non-existent classes and perfor... Daniel Kulp
- Re: Wrappers and non-existent classes and pe... Benson Margulies
