I think cycle.activate() just sets the next page, it doesn't
immediately send you there, so you're correct that the rest of the
code in your method will indeed run. If you need an immediate jump,
you have to throw a PageRedirectException. (This is also why, if you
need to redisplay the page you're on, you can do nothing. It will
automatically reappear.)
I, also, have been a little uncomfortable throwing an Exception for
something that's actually a normal and expected operation, but think
of this as similar to the EOFExceptions that some of the I/O classes
throw. It's just the way that a certain state change is signaled to
the framework.
Todd
On Jul 11, 2005, at 5:27 AM, Olasoji Ajayi wrote:
I am a tapestry newbie (a few weeks) and I am just developing my
first (test) application and I am enjoying it more than I did struts.
I discovered that IRequestCycle.activate() does not work with
PageValidate method, I had to throw a PageRedirect Exception
redirect to another page, with cycle.activate, nothing happens and
the program just goes to the next code.
id this the way it is designed or I am making a mistake somewhere?
cycle.activate worked for my listener object method, I kind of
prefer using it to direct to anther page to throwing exceptions.
I have also noticed that even after calling cycle.activate(), in
the middle of a listener method body, the next code still runs, I
was thinking that as soon as cycle.activate is called, that's the
end of life for the listener object.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
