Sebastien,

If you say "I don't know enough stripes to tell exactly what happens..." 
then why open a possibly "pointless" bug report and not post a question 
to Stripes user mailing list???

Personally, I am not surprised that the flashscope does not retain the 
messages across multiple redirects.  Why should it????

As far as your problem is concerned, a simple work around that should 
work would be to at the start of A2 processing simply grab all messages 
and add them again on A2... I haven't tried this mind you but I would 
guess that is what you want.

--Nikolaos





Sebastien Lorber (JIRA) wrote:
> Problem in flash scope and messages
> -----------------------------------
>
>                  Key: STS-812
>                  URL: http://www.stripesframework.org/jira/browse/STS-812
>              Project: Stripes
>           Issue Type: Bug
>           Components: Context Management
>     Affects Versions: Release 1.5
>          Environment: Any
>             Reporter: Sebastien Lorber
>
>
> There is a problem in the way messages are managed in flash scopes.
>
> Actually, when you add a message M1 on an action A1 and then redirect on the 
> action A2 that add a message M2, only the M2 message will be displayed on the 
> end page and M1 is lost.
> The M1 message is well displayed when you don't add M2 on A2.
>
> I don't know enough stripes to tell exactly what happens but all i know is 
> that the previous flashscope is well retrieved and contains M1 message.
>
> The request attribute "_stripes_defaultMessages" is well set with M1 on the 
> beginning of the GET call but i think it is being overriden with a new 
> collection containing only M2.
>
>
> I guess some fix could be to do some rework on 
> net.sourceforge.stripes.action.ActionBeanContext.getMessages(String)
> For exemple to have a system that takes messages from the previous scope and 
> add them to the current one.
>
>   

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to