When custom class loader in webapp context file is used and the context is being initialized and started, the custom classloader is just a substitution for the default webapp class loader, right ? But what are the consequences of doing this? Because, for instance, in Liferay portal an application can use custom PortalClassLoader, which just extends webapp class loader and does nothing else, it's the same class, no modifications at all. And I didn't find any following initializations like repository location changes etc. The point is, that the PortalClassLoader provides the webapp with an access to the ROOT portal context, which AFAIK doesn't use PortalClassLoader, according to debugger.