Really not the right approach. I strongly object to having a page poke around in the internals of another page ... for page-to-page interactions, the right approach is an event handler method on page A that injects and invokes methods on page B.
Alternately, you can build you own kind of interactions, by contributing your own Dispatcher to the MasterDispatcher service configuration. There are a number of reasonable approaches for doing this the right way, but having one page build event requests for components inside another page is not likely to work out well in the long run. At the very least, you will be exposing yourself to many internal APIs that are subject to change. On Mon, Sep 28, 2009 at 2:24 PM, Josh Canfield <j...@thedailytube.com> wrote: >> How do I trigger an action method in another page. > > Presuming Tapestry 5 take a look at ComponentEventLinkEncoder > > http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/services/ComponentEventLinkEncoder.html > > Josh > > On Mon, Sep 28, 2009 at 9:34 AM, Gunnar Eketrapp > <gunnar.eketr...@gmail.com> wrote: >> Hi! >> >> How do I trigger an action method in another page. >> >> I.e. navigate to some other page and execute an action method within it. >> >> Thanks in advance, >> Gunnar Eketrapp >> > > > > -- > -- > TheDailyTube.com. Sign up and get the best new videos on the internet > delivered fresh to your inbox. > > --------------------------------------------------------------------- > 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
