It is possible for scoped "forms", when using a ModelDriven action. Simply implement ScopedModelDriven and use the ScopedModelDrivenInterceptor to manage the form's scope. See the Struts 1 example in the showcase, where we use a session-scoped ActionForm without modifying the code at all. This technique can be used for any ScopedModelDriven action, not just Struts 1 actions.
Don On 10/11/06, Dave Newton <[EMAIL PROTECTED]> wrote:
From: Sébastien LABEY [mailto:[EMAIL PROTECTED] > Yes, I understand that, but it can be useful to specify the scope of an > action. For example, [...] I understand what you're saying, but you were never specifying the scope of an action. You could *use* it as that, but that wasn't its original purpose. IIRC you can set arbitrary params on an action in the struts config via the param element (although so far I am unable to retrieve these params within an interceptor, which is killing me for role-based authentication: if anybody has a canonical answer for this let me know.) Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
