[
https://issues.apache.org/jira/browse/WW-5850?focusedWorklogId=1053384&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1053384
]
ASF GitHub Bot logged work on WW-5850:
--------------------------------------
Author: ASF GitHub Bot
Created on: 08/Nov/26 10:04
Start Date: 08/Nov/26 10:04
Worklog Time Spent: 10m
Work Description: sonarqubecloud[bot] commented on PR #2130:
URL: https://github.com/apache/struts/pull/2130#issuecomment-6720140217
## [](https://sonarcloud.io/dashboard?id=apache_struts&pullRequest=2130)
**Quality Gate passed**
Issues
 [0 New
issues](https://sonarcloud.io/project/issues?id=apache_struts&pullRequest=2130&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [0 Accepted
issues](https://sonarcloud.io/project/issues?id=apache_struts&pullRequest=2130&issueStatuses=ACCEPTED)
Measures
 [0 Security
Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_struts&pullRequest=2130&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [0.0% Coverage on New
Code](https://sonarcloud.io/component_measures?id=apache_struts&pullRequest=2130&metric=new_coverage&view=list)
 [0.0% Duplication on New
Code](https://sonarcloud.io/component_measures?id=apache_struts&pullRequest=2130&metric=new_duplicated_lines_density&view=list)
<!
Issue Time Tracking
-------------------
Worklog Id: (was: 1053384)
Time Spent: 20m (was: 10m)
> Add declarative multi-step flows to ScopedModelDriven
> -----------------------------------------------------
>
> Key: WW-5850
> URL: https://issues.apache.org/jira/browse/WW-5850
> Project: Struts 2
> Issue Type: New Feature
> Components: Core, Core Interceptors, Plugin - Convention
> Reporter: Lukasz Lenart
> Assignee: Lukasz Lenart
> Priority: Major
> Fix For: 7.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Struts has two mechanisms for keeping form state across several requests
> (wizard-like flows): the {{scope}} interceptor ({{ScopeInterceptor}}) and the
> {{scopedModelDriven}} interceptor. This ticket gives {{scopedModelDriven}} an
> explicit flow lifecycle so it becomes a full alternative to {{scope}}.
> User poll on the mailing list: "Is anyone using the scope interceptor?"
> (user@, 2026-10-09). One reply, describing a multi-page form flow, which this
> feature covers.
> h2. Proposal
> A flow is a named set of actions sharing one model stored in the session.
> Each action declares the flow name and its role, in {{struts.xml}} or with a
> Convention annotation:
> * *start* — exactly one per flow. Begins the flow. Whether it creates a new
> model or picks up an existing one is configurable by the developer.
> * *step* — any number. Requires a running flow and works on the stored model.
> * *end* — any number. Requires a running flow; the model is removed from the
> session after the action runs.
> Behaviour:
> * A step or end action requested with no running flow redirects to the flow's
> start action.
> * Multiple flows can be defined in one configuration, distinguished by name.
> * One running flow per user per flow name.
> * Flow definitions are validated at startup (one start, at least one end,
> consistent model type).
> h2. Planned sequence for ScopeInterceptor
> * 7.6.0 — this ticket: the alternative ships. {{ScopeInterceptor}} is
> unchanged.
> * 7.7.0 — deprecate {{ScopeInterceptor}}, with a migration note to
> declarative flows.
> * 8.0.0 — remove {{ScopeInterceptor}}.
> h2. Out of scope
> * Deprecating or changing {{ScopeInterceptor}}.
> * Visualising flows (Config Browser plugin, IntelliJ IDEA plugin) — possible
> follow-up.
> * Independent concurrent runs of the same flow in one session (e.g. two
> browser tabs).
> * Application-scoped state.
> A design document will be attached via the pull request.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
