Tries to resolve a template.
The method arguments contain all the info needed for trying to
resolve the template. The Template Resolver will apply its configuration
(prefixes/suffixes, template mode patterns, cache configurations, etc) and
return a
TemplateResolution object.
The
ownerTemplate, which might be null, will be specified when the template
is resolved in order to be used as a fragent to be inserted into a higher level
template (the owner). Most template resolver implementations will simply ignore
this argument, but others might change their resolution results depending on the
owner template that is inserting the resolved fragment.
The fact that a Template Resolver returns a
TemplateResolution does not necessarily
mean that the resolved template resource exists. It might only be so if the template resolver
is configured to perform an existence check on the resource before returning a resolution
result (by means of calling
ITemplateResource#exists()), which might be configurable on
a per-
ITemplateResolver-implementation basis. Implementations might choose not to check
resource existance by default in order to avoid the possible performance impact of a double access
to the resource.
Note that the template selectors that might be used for a executing or inserting a template
are not specified to the template resolver. The reason is template selectors are applied by the parser,
not the template resolvers, and allowing the resolver to take any decisions based on template selectors
(like e.g. omitting some output from the resource) could harm the correctness of the selection operation
performed by the parser.