IIRC, if you use the Struts integration included with Spring
(DelegatingProxyAction) you can use instance variables in your actions.
Others more wiser than I
may can clarify
Limitations known
Bill
Joe Germuska wrote:
Action classes are pooled, not created anew for each request. Therefore,
use of
On Thu, 26 Aug 2004 11:01:33 -0500, Joe Germuska <[EMAIL PROTECTED]> wrote:
> Action classes are pooled, not created anew for each request.
> Therefore, use of instance variables runs a risk of synchronization
> problems, in much the same way as does the use of instance variables
> in servlets.
>
Action classes are pooled, not created anew for each request.
Therefore, use of instance variables runs a risk of synchronization
problems, in much the same way as does the use of instance variables
in servlets.
It seems as though there's not a whole lot of gain from pooling
Action classes, bu
As far as instances go, you should treat an Action the way you would a
servlet. The same instance is reused by Struts in responding to
multiple requests. Because of this, you can easily get conflicting
data when you use an Action instance variable for purposes specific to
a certain request.
For e
List
Oggetto: Instance variable is not recommended to be used in Action class
Can some one tell me why the above is correct? Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
Can some one tell me why the above is correct? Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
6 matches
Mail list logo
