2010/11/25 Thiago H. de Paula Figueiredo <[email protected]> > On Wed, 24 Nov 2010 21:51:18 -0200, Katia Aresti <[email protected]> > wrote: > > You are using the wrong list, you should post this questions into the >> "Tapestry users" <[email protected]> >> > > Absolutely correct. > > > My answer : I would use input parameters (emulating the pagelink component >> that gets the page as an input parameter). You could easily pass two params. >> > > Or trigger and event and use the value returned by the method that handle > to event as a way to decide which page to show next. >
There are always several ways to do the same thing. @Thiago Doing with events like this, does not come up to the same thing ? In the end I have to catch the event on my page to decide where to go. So, why not telling the component from the beginning where to go ? I mean, why complicating life defining new events handling, triggering and catching for this use case ? Isn't it more simple and more readable to tell the login form where to go from the beginning ? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br >
