Hi, We are considering deprecating the "scope" interceptor (org.apache.struts2.interceptor.ScopeInterceptor) and removing it in a future major release. It is the interceptor you add with <interceptor-ref name="scope"/>. It copies a listed set of action properties to and from the session or application scope, and is meant for wizard-like flows. It came over largely unchanged from WebWork 2.2 and has seen little maintenance since. It is not part of any default stack. There are alternatives for the same job: - ScopedModelDriven (the "scopedModelDriven" interceptor), which keeps the action's model in the session across requests - a session-scoped bean, or reading and writing session values through SessionAware
Before we decide, we would like to know whether anyone still relies on it. If you use it, please reply and tell us what you use it for, especially if the alternatives above would not work for you. Thanks in advance! Lukasz
