Otho is exactly right here. Each piece of Tapestry has its purpose, and pages act as a bridge between the client and the components within the page.
On Mon, Sep 14, 2009 at 4:13 AM, Otho <taa...@googlemail.com> wrote: > I wouldn't couple a component so tightly to a specific page. If you need to > pass certain bits of information you can also use component parameters from > within the page. > > 2009/9/14 chakra <chakri.tut...@gmail.com> > > > > > thanks for the responses. > > Is there any plan in future releases of tapestry, to add support for > > onActivate method in components also,to get the page context? > > > > That will make life much easier. > > > > Chakra > > -- > > View this message in context: > > > http://www.nabble.com/Accessing-page-context-from-a-component-tp25422102p25433429.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
