Feature Request: Feature-Flagged Direct JSF Mount for SPA Tree View (with iframe Fallback) #12179
Description
Overview of the Feature Request
Add a Dataverse JSF integration path to mount a SPA tree-view module directly in JSF (without iframe) behind a feature flag, while keeping iframe fallback for compatibility.
Important scope boundary:
- This issue is for the JSF mount/reuse contract and rollout path.
- Tree-view feature implementation itself remains in the SPA workstream.
Proposed scope:
- Define JSF container + bootstrap contract for mounting the SPA tree-view module.
- Add feature flag to switch between direct mount and iframe fallback.
- Define config/input and completion/event contract between JSF and SPA.
- Keep backwards-compatible fallback path.
What kind of user is the feature intended for?
Depositor, Curator, Sysadmin
What inspired the request?
We want to implement complex UI logic once in SPA and reuse it in JSF, instead of duplicating feature logic across frontends. Tree view is the first target for this reuse pattern.
What existing behavior do you want changed?
Today, embedding patterns are mainly iframe-oriented and not a standardized direct JSF mount contract for SPA modules.
Any brand new behavior do you want to add to Dataverse?
Yes:
- Feature-flagged direct JS mount path in JSF for tree-view module reuse.
- Standardized integration contract for SPA module config/events.
- iframe fallback for compatibility and rollout safety.
Any open or closed issues related to this feature request?
- Allow selecting of files in Tree View to Edit or Download #6691
- Feature Request/Idea: reusing file upload page as dvwebloader dataverse-frontend#468
Are you thinking about creating a pull request for this feature?
Yes. This is planned as part of the tree-view integration track, separate from tree-view SPA implementation details.