anchor.diff:  The `ClassPathXmlApplicationContext` exposes a number of constructors to enable
   convenient instantiation. The basic idea is that you can supply merely a string array
   that contains only the filenames of the XML files themselves (without the leading path
  -information) and also supplies a `Class`. The `ClassPathXmlApplicationContext`
  -then derives the path information from the supplied class.
  +information) and also supply a `Class`. The `ClassPathXmlApplicationContext` then derives
  +the path information from the supplied class.
   
   Consider the following directory layout:
   
   [literal,subs="verbatim,quotes"]
   ----
   com/
  -  foo/
  +  example/
       services.xml
  -    daos.xml
  +    repositories.xml
       MessengerService.class
   ----
   
  -The following example shows how a `ClassPathXmlApplicationContext` instance composed of the beans defined in
  -files named `services.xml` and `daos.xml` (which are on the classpath) can be instantiated:
  +The following example shows how a `ClassPathXmlApplicationContext` instance composed of
  +the beans defined in files named `services.xml` and `repositories.xml` (which are on the
  +classpath) can be instantiated:
   
   [source,java,indent=0,subs="verbatim,quotes",role="primary"]
   .Java
   ----
   	ApplicationContext ctx = new ClassPathXmlApplicationContext(
  -		new String[] {"services.xml", "daos.xml"}, MessengerService.class);
  -----
  -[source,kotlin,indent=0,subs="verbatim,quotes",role="secondary"]
  -.Kotlin
  -----
  -	val ctx = ClassPathXmlApplicationContext(arrayOf("services.xml", "daos.xml"), MessengerService::class.java)
  +		new String[] {"services.xml", "repositories.xml"}, MessengerService.class);
  +----
  +[source,kotlin,indent=0,subs="verbatim,quotes",role="secondary"]
  +.Kotlin
  +----
  +	val ctx = ClassPathXmlApplicationContext(arrayOf("services.xml", "repositories.xml"), MessengerService::class.java)
   ----
   
   See the {api-spring-framework}/context/support/ClassPathXmlApplicationContext.html[`ClassPathXmlApplicationContext`]
  
positive.code: === Wildcards in Application Context Constructor Resource Paths
  
  The resource paths in application context constructor values may be simple paths (as
  shown earlier), each of which has a one-to-one mapping to a target `Resource` or, alternately, may
  contain the special "classpath*:" prefix or internal Ant-style regular expressions
  (matched by using Spring's `PathMatcher` utility). Both of the latter are effectively
  wildcards.
  
  One use for this mechanism is when you need to do component-style application assembly. All
  components can 'publish' context definition fragments to a well-known location path, and,
  when the final application context is created using the same path prefixed with
  `classpath*:`, all component fragments are automatically picked up.
  
  
negative.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
  