Resolve views from dedicated folder
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
The Facelets VDL will by default try to resolve a view in the root of a web application or in META-INF/resources of a jar file (where the jar location automatically follows from using ServletContext#getResource)
In addition to this primary location I would like to propose loading views from a dedicated folder called "/views". This should be done in analogy to how contracts are loaded from "/contracts" and resources from "/resources", including the ability to let a user configure an alternative location.
The use case for this is letting the user easily configure a _simple_ alternative location from where views are loaded and opening up more advanced processing by the runtime.
This more advanced processing is not part of this issue. This issue is strictly about providing a folder from which views (and only views) can be loaded.
Note that this issue is split-off from #1099, which asked about this folder but also asked about the advanced processing.
Contributor guide
Research direction
Start by tracing Facelets VDL view resolution and the existing loading paths for /contracts and /resources, including their alternative-location configuration. Check how ServletContext#getResource is used for the current root and META-INF/resources locations. Done means views can also load from /views, or a configured alternative location, without changing loading behavior for non-view resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100