> Request != render. A request can have rendering, but their not the same. Yes of course, I was talking about the scope of the service "Environmental services are, by their nature, per-thread (and therefore per-request).", so are @PageAttached and @PageLoaded triggered on every Request.
> A page *is* a component, so there's no conflict here. I guess the > documentation is trying to say that the Environmental annotation does > not work in services. Yes Thiago, but this is not what it is actually saying is it? How would a new user catch this? ----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Friday, 19 June, 2009 18:00:59 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: RenderSupport in pages? On Fri, Jun 19, 2009 at 11:42 AM, <p.stavrini...@albourne.com> wrote: > In this case it seems that Tapestry doesn't like it when you use @PageLoaded > or @PageAttached, though I can't explain why this wouldn't work... Not exactly. @PageLoaded and @PageAttached are triggered before rendering, and RenderSupport is only available while rendering. A better event for what you want would be @BeforeRender. > No, not at all I have done this too. I don't know what to make of the docs, > they seem a bit conflicting: "The Environmental annotation only works inside > components." well this is not true, I am using it in pages without problems. A page *is* a component, so there's no conflict here. I guess the documentation is trying to say that the Environmental annotation does not work in services. > @Environmental works per request, and so does @PageAttached and @PageLoaded, > so it is a bit of a puzzle... although these are not really the render > phase methods with which RenderSupport is best suited for. Request != render. A request can have rendering, but their not the same. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org