[
https://issues.apache.org/jira/browse/WW-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Lenart updated WW-5863:
------------------------------
Description:
h2. Goal
Announce the removal planned in WW-5862 (8.0.0) one release ahead. WW-5850
(7.6.0) adds declarative multi-step flows with a dedicated {{flow}}
interceptor, which covers the wizard-style use the {{scope}} interceptor was
written for.
A usage poll on the user list (2026-10-09) showed the interceptor is still used
for multi-page forms, so it is deprecated with a replacement in place and not
removed outright.
h2. Scope
* Add {{@Deprecated(since = "7.7.0", forRemoval = true)}} and a Javadoc
deprecation note pointing to the flow interceptor on {{ScopeInterceptor}} and
{{ScopeInterceptorCacheDestroyable}}
* Log a warning when the interceptor is initialised, so applications that use
it see the deprecation at startup
* Mark the scope interceptor page on the site as deprecated and link the flow
interceptor
* Add a 7.7.0 migration note describing how a {{scope}} configuration maps to a
flow
h2. Known limitation, documented and not fixed
The Javadoc and the site page state that the interceptor uses session-level
locking and that each action execution is atomic at the session level. This
does not hold:
* the lock is taken on the session map of the action context, and a new session
map is created for every request, so two requests of the same HTTP session
never wait for each other
* the lock is released three times per invocation (before the result, after the
invocation and in the final cleanup) without checking which invocation holds it
The locking is not reworked, since the interceptor is going away. As part of
this ticket the locking statement is removed from the Javadoc and the site
page, and the migration note says that concurrent requests of one session were
never serialised.
The repeated lock release was reported by Dũng Khắc.
Related: WW-5862, WW-5850, WW-5826
was:
h2. Goal
Announce the removal planned in WW-5862 (8.0.0) one release ahead. WW-5850
(7.6.0) adds declarative multi-step flows with a dedicated {{flow}}
interceptor, which covers the wizard-style use the {{scope}} interceptor was
written for.
A usage poll on the user list (2026-10-09) showed the interceptor is still used
for multi-page forms, so it is deprecated with a replacement in place and not
removed outright.
h2. Scope
* Add {{@Deprecated(since = "7.7.0", forRemoval = true)}} and a Javadoc
deprecation note pointing to the flow interceptor on {{ScopeInterceptor}} and
{{ScopeInterceptorCacheDestroyable}}
* Log a warning when the interceptor is initialised, so applications that use
it see the deprecation at startup
* Mark the scope interceptor page on the site as deprecated and link the flow
interceptor
* Add a 7.7.0 migration note describing how a {{scope}} configuration maps to a
flow
h2. Known limitation, documented and not fixed
The Javadoc and the site page state that the interceptor uses session-level
locking and that each action execution is atomic at the session level. This
does not hold:
* the lock is taken on the session map of the action context, and a new session
map is created for every request, so two requests of the same HTTP session
never wait for each other
* the lock is released three times per invocation (before the result, after the
invocation and in the final cleanup) without checking which invocation holds it
The locking is not reworked, since the interceptor is going away. As part of
this ticket the locking statement is removed from the Javadoc and the site
page, and the migration note says that concurrent requests of one session were
never serialised.
Related: WW-5862, WW-5850, WW-5826
> Deprecate the scope interceptor
> -------------------------------
>
> Key: WW-5863
> URL: https://issues.apache.org/jira/browse/WW-5863
> Project: Struts 2
> Issue Type: Task
> Components: Core Interceptors
> Reporter: Lukasz Lenart
> Priority: Major
> Fix For: 7.7.0
>
>
> h2. Goal
> Announce the removal planned in WW-5862 (8.0.0) one release ahead. WW-5850
> (7.6.0) adds declarative multi-step flows with a dedicated {{flow}}
> interceptor, which covers the wizard-style use the {{scope}} interceptor was
> written for.
> A usage poll on the user list (2026-10-09) showed the interceptor is still
> used for multi-page forms, so it is deprecated with a replacement in place
> and not removed outright.
> h2. Scope
> * Add {{@Deprecated(since = "7.7.0", forRemoval = true)}} and a Javadoc
> deprecation note pointing to the flow interceptor on {{ScopeInterceptor}} and
> {{ScopeInterceptorCacheDestroyable}}
> * Log a warning when the interceptor is initialised, so applications that use
> it see the deprecation at startup
> * Mark the scope interceptor page on the site as deprecated and link the flow
> interceptor
> * Add a 7.7.0 migration note describing how a {{scope}} configuration maps to
> a flow
> h2. Known limitation, documented and not fixed
> The Javadoc and the site page state that the interceptor uses session-level
> locking and that each action execution is atomic at the session level. This
> does not hold:
> * the lock is taken on the session map of the action context, and a new
> session map is created for every request, so two requests of the same HTTP
> session never wait for each other
> * the lock is released three times per invocation (before the result, after
> the invocation and in the final cleanup) without checking which invocation
> holds it
> The locking is not reworked, since the interceptor is going away. As part of
> this ticket the locking statement is removed from the Javadoc and the site
> page, and the migration note says that concurrent requests of one session
> were never serialised.
> The repeated lock release was reported by Dũng Khắc.
> Related: WW-5862, WW-5850, WW-5826
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)