ok, this is the obvious candidate if I want to make it 'by hand'. Some little method in the base action or filter that takes care for it as I would do it in Struts 1.
But I thought about something ... out of the box. I do not need to make extra redirect through the browser, I want to switch to another action in the same request - and in such case it should be possible to do it without playing with session. I tried to play with the result of type 'chain' but I only got exceptions. I am not sure if I understand 'chain' as it did not work for me. Thanks for your valuable tips. They are valuable. I will use the session approach probably, fits most use cases, but I was wondering if it is possible to reuse the messages/errors in the same request across different actions. Best regards Dariusz Wojtas On 12/30/06, Nick Tucker <[EMAIL PROTECTED]> wrote:
Hi You could put the message in a session attribute and then get the second action to check for the attribute and display it if found (remembering to remove it once displayed) . How to get access to the session is in the Struts 2 faq. Nick Dariusz Wojtas wrote: > > Excellent hint, thanks. > I forgot I may jump between various methods this way in the struts config. > This will perfectly work in the case I described. > > Any idea how to solve the problem with various messages or errors to > be displayed, when I have no control on the messages/errors being > added? > > Dariusz Wojtas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]