- All Known Implementing Classes:
public interface RequestPageCachePer-thread service that caches page instances for the duration of the request, and is also responsible for tracking the active page (the page which will ultimately render the response). Since
Pageis internal, most user-code should use the
ComponentSourceservice instead. Starting in 5.2, page instances are shared (with externalized mutable state), not pooled, but the cache is still useful for managing the page's lifecycle.
getGets the page via its page name, in the current locale. The logical page name is resolved to a class name, which is used to obtain the page (from the page pool). Note that under certain circumstances, a page may have multiple names (even beyond simple case-insensitivity), and RequestPageCache caches correctly.
pageName- the name of the page to retrieve (this is the logical page name, not the fully qualified class name)
- a page instance reserved for this request
IllegalArgumentException- if the name can not be resolved to a page instance