On Thu, 25 Nov 2010 10:08:19 -0200, Katia Aresti <[email protected]>
wrote:
There are always several ways to do the same thing.
Agreed. :)
@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 ?
I guess you're right. When I read your message, I've read "parameter" as
"query parameter", not as "component parameter". (facepalm)
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
