Howard- thanks. In the meantime, have any suggestions to get any kind of redirect working so I don't end up with page navigation as POSTs instead of GETs? I had this working in Tap 3 and just moved to 4. I am attempting redirects from validate listeners and other listeners like for image submits. I am throwing a PageRedirectException from my Home.pageValidate() and it seems to work, such that when I refresh this new page(call it PlaceOrder), there is no POST warning dialog from my browser. Throwing a PageRedirectException from a listener in the PlaceOrder page does go to the next page (call it PayOrder) and leaves it so that a refresh gives me the post warning dialog. I am attempting to do the same as a the POST Redirect GET pattern.
Thanks, Joseph On 9/28/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > On 9/28/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > Many have stated that using exceptions for this purpose (redirecting) > > is a mistake. > > > > They are right. > > To be clear; I meant the Tapestry API is flawed, not the way people > are using it. > > > > > In the meantime, add a bug and I'll check the affected code to > > properly throw the RedirectException (currenlty, there are > > catch/rethrows for PageRedirectException). > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
