- All Superinterfaces:
- All Known Implementing Classes:
public interface ResourcePatternResolver extends ResourceLoaderStrategy interface for resolving a location pattern (for example, an Ant-style path pattern) into Resource objects.
This is an extension to the
ResourceLoaderinterface. A passed-in ResourceLoader (for example, an
org.springframework.context.ApplicationContextpassed in via
org.springframework.context.ResourceLoaderAwarewhen running in a context) can be checked whether it implements this extended interface too.
PathMatchingResourcePatternResolveris a standalone implementation that is usable outside an ApplicationContext, also used by
ResourceArrayPropertyEditorfor populating Resource array bean properties.
Can be used with any sort of location pattern (e.g. "/WEB-INF/*-context.xml"): Input patterns have to match the strategy implementation. This interface just specifies the conversion method rather than a specific pattern format.
This interface also suggests a new resource prefix "classpath*:" for all matching resources from the class path. Note that the resource location is expected to be a path without placeholders in this case (e.g. "/beans.xml"); JAR files or classes directories can contain multiple files of the same name.
Fields Modifier and Type Field and Description
CLASSPATH_ALL_URL_PREFIXPseudo URL prefix for all matching resources from the class path: "classpath*:" This differs from ResourceLoader's classpath URL prefix in that it retrieves all matching resources for a given name (e.g.
static final String CLASSPATH_ALL_URL_PREFIXPseudo URL prefix for all matching resources from the class path: "classpath*:" This differs from ResourceLoader's classpath URL prefix in that it retrieves all matching resources for a given name (e.g. "/beans.xml"), for example in the root of all deployed JAR files.
Resource getResources(String locationPattern) throws IOExceptionResolve the given location pattern into Resource objects.
Overlapping resource entries that point to the same physical resource should be avoided, as far as possible. The result should have set semantics.
locationPattern- the location pattern to resolve
- the corresponding Resource objects
IOException- in case of I/O errors