You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ServletContext has a method to acquire all paths to resources within a web application; getResourcePaths().
In JSF resources are handled by the ResourceHandler This has a method createViewResource that takes a path and effectively returns a URL, just like ServletContext has a getResource method taking a path and returning a URL.
In both cases, the usage is to abstract the actual location of resources, which could therefor transparently be on a local or remote filesystem, in a database, custom jar location, or whatever.
The JSF specific ResourceHandler however does not have a getResourcePaths() equivalent.
I'd like to propose to rectify this by introducing such method for JSF view resources.
Care should be taken that it can both physical and logical views, and both views that can be requested for a top level request only, and all views (including those for includes).
The text was updated successfully, but these errors were encountered:
The ServletContext has a method to acquire all paths to resources within a web application; getResourcePaths().
In JSF resources are handled by the ResourceHandler This has a method createViewResource that takes a path and effectively returns a URL, just like ServletContext has a getResource method taking a path and returning a URL.
In both cases, the usage is to abstract the actual location of resources, which could therefor transparently be on a local or remote filesystem, in a database, custom jar location, or whatever.
The JSF specific ResourceHandler however does not have a getResourcePaths() equivalent.
I'd like to propose to rectify this by introducing such method for JSF view resources.
Care should be taken that it can both physical and logical views, and both views that can be requested for a top level request only, and all views (including those for includes).
The text was updated successfully, but these errors were encountered: