Hi, this is more a question of technique than an actual problem. Some use cases: Lets say I have code that throws a NPE. I'd get a Tapestry error page that spills it's guts. It must use some technique for redirecting to another page at any point (might be too deep in the framework to harness that power)
Lets say I have another page that requires a user session (ASO) -- the OnActivate method would do the checking and redirect to a page from there. Anyone can do this from OnActivate--so long as you know everything in the OnActivate() method, so it's not really interesting. Now lets say I have a page or component that checks a value that we could label as invalid, or we have a select component that can't be filled because a DB is down. Is there a way to redirect to another page at any point in the render process of a component or page? I think this would kind of fall along the lines of people who questioned how to replace the Tapestry error page with something more appropriate for the end user. Except that I'd want to be able to explicitly call/forward to an arbitrary page when my code comes across something abnormal. Does anyone have ideas or strategies about this? Daniel Jue --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
