anchor.diff:  classpath:com/mycompany/**/applicationContext.xml
   ----
   
  -When the path location contains an Ant-style pattern, the resolver follows a more complex procedure to try to resolve the
  -wildcard. It produces a `Resource` for the path up to the last non-wildcard segment and
  -obtains a URL from it. If this URL is not a `jar:` URL or container-specific variant
  -(such as `zip:` in WebLogic, `wsjar` in WebSphere, and so on), a `java.io.File` is
  -obtained from it and used to resolve the wildcard by traversing the filesystem. In the
  -case of a jar URL, the resolver either gets a `java.net.JarURLConnection` from it or
  -manually parses the jar URL and then traverses the contents of the jar file to resolve
  -the wildcards.
  +When the path location contains an Ant-style pattern, the resolver follows a more complex
  +procedure to try to resolve the wildcard. It produces a `Resource` for the path up to the
  +last non-wildcard segment and obtains a URL from it. If this URL is not a `jar:` URL or
  +container-specific variant (such as `zip:` in WebLogic, `wsjar` in WebSphere, and so on),
  +a `java.io.File` is obtained from it and used to resolve the wildcard by traversing the
  +filesystem. In the case of a jar URL, the resolver either gets a
  +`java.net.JarURLConnection` from it or manually parses the jar URL and then traverses the
  +contents of the jar file to resolve the wildcards.
   
   [[resources-app-ctx-portability]]
   ===== Implications on Portability
  
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: Such a resource may be in only one location, but when a path such as the preceding example
  is used to try to resolve it, the resolver works off the (first) URL returned by
  `getResource("com/mycompany");`. If this base package node exists in multiple
  `ClassLoader` locations, the actual end resource may not be there. Therefore, in such a case
  you should prefer using `classpath*:` with the same Ant-style pattern, which
  searches all class path locations that contain the root package.
  
  