You want to generate two links that are handled differently. Either put a context value into each EventLink, or switch to ActionLink which makes it easy to distinguish the two, by component id. Got duplicate code? Refactor it into a common method.
2011/7/28 Михаил Слободянюк <slobodyanu...@gmail.com>: > Hi! > If you want debug event call order read > http://tapestry.apache.org/logging.html Component Event Debugging part > > Mihail. > > 2011/7/28 nillehammer <tapestry.nilleham...@winfonet.eu> > >> It sounds like this could be achieved by providing two event handlers, one >> for each button code could look like: >> @OnEvent(value="firstEventLink'sEventValue") >> final void/Class/Block/Object displaySpecialValue(final MarkupWriter >> writer) >> { >> ..... >> } >> >> @OnEvent(value="secondEventLink'sEventValue") >> final void/Class/Block/Object displayAnotherSpecialValue(final MarkupWriter >> writer) { >> ..... >> } >> >> ----- >> http://www.winfonet.eu >> -- >> View this message in context: >> http://tapestry.1045711.n5.nabble.com/Triggered-event-check-on-page-tp4642223p4642318.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 >> >> > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
