I got an error 500 when I tested the prgtoolkit.htm application entering "123" for the value of a new Item. It had a security error in the bean utils. I don't know the security model yet and am just starting out so I can't tell you why it happened. Just letting you know since you've told us to look at this web application.
Michael -----Message d'origine----- De : Matthew Ryan [mailto:[EMAIL PROTECTED] Envoyé : jeudi 20 janvier 2005 07:00 À : Struts Users Mailing List; [EMAIL PROTECTED] Objet : Re: Post -> Redirect -> Get HI Craig, Thanks for the reply. Recently I had a read of these articles on theServerSide by Michael Jouravlev, titled 'Redirect After Post' and 'Redirect After Post 2'. http://www.theserverside.com/articles/content/RedirectAfterPost/article.html http://www.theserverside.com/articles/article.tss?l=RedirectAfterPost2 As well as a look at the sample application at : http://www.superinterface.com/projects/prgtoolkit.htm All of which built on Struts. The impetus for asking was mainly to see how far some others might take PRG or the issues that it tries to deal with. Thanks again Craig. Matthew Quoting Craig McClanahan <[EMAIL PROTECTED]>: > On Thu, 20 Jan 2005 13:27:59 +1000, Matthew Ryan > <[EMAIL PROTECTED]> wrote: > > Want to ask if many people implement something of a PRG in the handling of > > Actions (and forwards)? > > It is, of course, easy to implement this ... just set redirect="true" > on your forwards and you get the PRG result. But it comes with costs: > the increased network bandwidth of the extra round trip, but (more > importantly for a Struts app) the loss of the ability to use request > scope attributes to pass information to the new page. > > Personally, my Struts apps use transaction tokens to guard against > duplicate submits, which deals with the most egregious of the problems > that PRG addresses. (And yes, that means I care very little about the > URLs that are displayed -- in a web *application* instead of a web > *site*, URLs should be considered an implementation detail :-). > > Craig > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
