Spring管理的Struts 2 Action类bean的适当范围应该是什么？

Question

In a Spring managed Struts 2 application, the HttpServletRequest objects are stored as a global variable inside the Action classes. After doing some research I found that by default Struts Action classes are thread safe as they are instantiated for every request, but in the scenario described above, the Struts Action classes are configured as Spring beans without mentioning the bean scope(So by default they are singletons). I think this is a recipe for a disaster, so I was searching for a fix and I found the following in the official Struts 2 Spring integration example below:

<bean id="editService" class="org.apache.struts.edit.service.EditServiceInMemory"/>

<bean id="editAction" class="org.apache.struts.edit.action.EditAction" scope="prototype">

    <property name="editService" ref="editService" />

</bean>

Here the scope is set to prototype but I thing it should be request as the action class needs to instantiated for every Http request. Please tell me whether my understanding is correct and if it is the correct solution, other than instantiating the request objects as local variables.

I had found the following question in stack overflow but I want to know in terms of Struts 2: Spring Request and Prototype Scope?

Answer 1

This post explains pretty clearly how the two work: Spring Request and Prototype Scope?

I would say that if your app only uses simple actions, it really doesn't matter which you use. If you are using filters or struts interceptors and want to hold state between different steps in the request pipeline, then you must use request scoped beans. Otherwise it again doesn't matter.

I would probably use prototype based beans when request based ones weren't absolutely necessary.