Re: PRG pattern question

2010-05-31 Thread Chris Pratt
If you want to implement the PRG pattern, I only see two possibilities. Either you put the information in the session to preserve it from the P to the G or you put hidden parameters in a form on the page. It's a lot more secure keeping the data on the server side. But I could be missing an option

Re: PRG pattern question

2010-05-31 Thread szerintedmi
Alex Rodriguez Lopez To: user@struts.apache.org Date: Thu, 27 May 2010 13:15:14 +0100 Subject: Re: PRG pattern question Em 26-05-2010 16:57, Chris Pratt escreveu: > If you search the forum, someone posted an Interceptor (quite a while ago) > that saves the Action/Field Errors/Message

Re: PRG pattern question

2010-05-27 Thread Alex Rodriguez Lopez
Em 26-05-2010 16:57, Chris Pratt escreveu: If you search the forum, someone posted an Interceptor (quite a while ago) that saves the Action/Field Errors/Messages in the Session so that they will survive a redirect. It could easily be extended to do what you require. (*Chris*) I think this i

Re: PRG pattern question

2010-05-26 Thread Chris Pratt
If you search the forum, someone posted an Interceptor (quite a while ago) that saves the Action/Field Errors/Messages in the Session so that they will survive a redirect. It could easily be extended to do what you require. (*Chris*) On Wed, May 26, 2010 at 5:45 AM, szerintedmi wrote: > Hi Ev

Re: PRG pattern question

2010-05-26 Thread Greg Lindholm
I don't believe there is any canned "best practice" solution for this issue. My apps do the same thing; on a successful post I redirect to a get, on a validation error they simply forward back to the jsp so as to preserve the input data. It is possible to manually include all your form fields data

PRG pattern question

2010-05-26 Thread szerintedmi
Hi Everybody, I would like to ask some advice implementing PRG pattern with struts2 (using 2.0.14). I can easily handle a normal scenario : 1.GET showItem.action?itemId=1 result: showItem.jsp 2. POST saveItem.action result: redirect-action: success?itemId=1 3. GET success?itemId =1 result