Hi, i'm trying to implement a situation where as, i have a PageA, PageB and
PageC.  When using PageA, depending on different situations, i would want
the page to render, otherwise, it would want to render PageC.

What happen's in real life is :
Start of with PageA::onActivate(), the conditions don't apply for a
redirection to PageC, so PageA is rendered.  On PageA, i've got a PageLink
that brings me to PageB.  When i click on it, PageA::onActivate() is called,
and at this point, the conditions apply for a redirection to PageC, so PageB
is never called (since i clicked on the PageLink, i want to show PageB, but
the onActivate is called and i don't have a way to determine if it's from
the PageLink).

Everywhere i read, it's suggested that the onActivate : <&lt;A good
&quot;rule of thumb&quot; is to use onActivate(...) and onPassivate() for no
more than receiving and returning the activation context.
In this page, for example, onActivate(...) receives a person id and
onPassivate() returns a person id. It can be tempting to put setup code into
onActivate(...) but avoid this because onActivate(...) is called very
often&quot; &gt;> 
http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/onactivateandonpassivate/3
Jumpstart - PageNavigation .

Question #1 : Why is the onActivate() called when choosing the PageLink ?

Question #2 : What other way can i redirect a to another page without using
onActivate ?

Thank you for your time

Rene

--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Page-redirection-tp4778938p4778938.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to