anchor.diff:  	public interface ResourceLoader {
   
   		Resource getResource(String location);
  +
  +		ClassLoader getClassLoader();
   	}
   ----
   [source,kotlin,indent=0,subs="verbatim,quotes",role="secondary"]
   .Kotlin
   ----
  -interface ResourceLoader {
  -
  -	fun getResource(location: String): Resource
  -}
  +	interface ResourceLoader {
  +
  +		fun getResource(location: String): Resource
  +
  +		fun getClassLoader(): ClassLoader
  +	}
   ----
   
   All application contexts implement the `ResourceLoader` interface. Therefore, all
  
positive.code: [NOTE]
  ====
  The scanning of classpath packages requires the presence of corresponding directory
  entries in the classpath. When you build JARs with Ant, do not activate the files-only
  switch of the JAR task. Also, classpath directories may not get exposed based on security
  policies in some environments -- for example, stand-alone applications on JDK 1.7.0_45
  and higher (which requires 'Trusted-Library' to be set up in your manifests. See
  
negative.code: `ApplicationContext` interface.
  
  In application components, you may also rely upon autowiring of the `ResourceLoader` as
  an alternative to implementing the `ResourceLoaderAware` interface. The _traditional_
  `constructor` and `byType` autowiring modes (as described in <<beans-factory-autowire>>)
  are capable of providing a `ResourceLoader` for either a constructor argument or a
  setter method parameter, respectively. For more flexibility (including the ability to
  