Do you understand /why/ we're saying it? IMO it'd be beneficial to
understand why you're seeing a "change" in behavior.

Dave
 On Jul 12, 2011 1:17 PM, "Emi Lu" <em...@encs.concordia.ca> wrote:
> Thank you for all inputs! All right, I will have to change my codes.
>
> Emi
>
>
> On 07/12/2011 12:57 PM, stanl...@gmail.com wrote:
>> Dave is right Emi. I have been working with other frameworks recently,
and
>> what Struts/2 needs is a simple FlashScope that allows a request to last
two
>> life-cycles. However, unless you were doing something OOTO, a request in
>> Struts/2 lasts for one reqest/response trip.
>>
>> Peace,
>> Scott
>>
>> On Tue, Jul 12, 2011 at 11:14 AM, Dave Newton<davelnew...@gmail.com>
wrote:
>>
>>> On Tue, Jul 12, 2011 at 12:05 PM, Emi Lu wrote:
>>>>> Because it's a redirect, and things in the request go away when
>>>>> there's a new request.
>>>> Not true for previous version.
>>>
>>> Previous version had a bug, then, because by default, anything
>>> relating to an action's instantiation should go away during a
>>> redirect--that's kind of the point of instantiating an
>>> action-per-request.
>>>
>>> Again, the only way this *should* be possible is by (incorrectly, IMO)
>>> using singleton actions (Bad Idea) or a scope intereptor (or
>>> equivalent). Are you using Spring?
>>>
>>> Please zip up a (maven-ized) minimal example showing the behavior;
>>> I'll change the S2 version to the two you mention and debug
>>> this--messages should *not* persist between requests.
>>>
>>> Dave
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
>>> For additional commands, e-mail: user-h...@struts.apache.org
>>>
>>>
>>
>
>
> --
> Emi Lu, ENCS, Concordia University, Montreal H3G 1M8
> em...@encs.concordia.ca +1 514 848-2424 x5884
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>

Reply via email to