has anyone else stumbled over cycle.setPage vs. PageRedirectExcep tion?
Phil Surette <[email protected]>
| Newsgroups | gmane.comp.java.tapestry.devel |
|---|---|
| Message-ID | <[email protected]> |
The tutorial uses cycle.setPage to switch pages in a listener, so that's what I normally do. During a request cycle, you need to throw RedirectExceptions to move to a different page - cycle.setPage in beginResponse, for instance, has no effect. I think you should be able to use the same technique in either situation - set up a page, call a method to move to that page (IMO you shouldn't need to throw an exception in either case). How about a redirect method in IPage? Then it's always obvious how to switch pages. Behind the scenes, I suppose redirect could always throw a PageRedirectException. Does anyone else have an opinion on/care about this? I only mention it because I have fumbled around more than once before remembering about PageRedirectException.