Thanks ! Pardon me ... i have not looked into the Ajax support that you have built into tapestry...but we have lots of ajax-related requirement and I would need all of that real soon. Say I later choose to render this component in response to ajax request, then I wonder if the PageBeginRenderListener notion sounds a little odd? as there is only one page in my application which has already rendered and from then on i will be just refreshing the embedded components on ajax request? ah and while we are at that ..will PageBeginRenderListener be called when rendering a component in ajax context?..just to make sure that my stuff will continue to work after i integrate your library.
thanks, Karthik On 12/15/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I think the context of saying "this page is about to render" is true no matter which object you attach the listener to. On 12/14/06, karthik G <[EMAIL PROTECTED]> wrote: > Hi All, > > I understand that PageBeginRenderListener gets called during render and > rewind of a Page. I later created a component that is embedded inside a page > and moved the content from the Page to the newly created Component. Now my > component implements PageBeginRenderListener and does everything that was > being done by the page earlier. > > But it looks very odd in the Component as it is not a Page and still > implements PageBeginRenderListener. I do realize that the Component is > rendered in a Page context. May be its a stupid question - Do we have a > ComponentBeginRenderListener or something of that sort? > > thanks, > Karthik > > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
