Thanks for the reply Thiago.
One simple question related to this: if I have a service that is used by
many components and that holds a list of component related information,
how do I make this request related? That is, if I want i.e. have a list
of all those components nested ids for a given request (they send that
when
they register themselves at beginRender) then how do I clear that list
at
the beginning or end of the request inside the service? How do I make
sure
that I keep that information request relative since the service is a
singleton.
Thanks,
Andreas Pardeike
On 29 sep 2009, at 16.00, Thiago H. de Paula Figueiredo wrote:
Em Tue, 29 Sep 2009 03:21:40 -0300, Andreas Pardeike <fsys....@gmail.com
> escreveu:
Thiago,
Hi!
I have a test version up in a project and I wonder why Tapestry
does not support this kind of loose event handling where
components register themselves for zone refreshes or method calls
that are related to events.
I guess that's because loose event handling is against Tapestry's
philosophy to not be loose and provide a very robust error checking.
I think you can implement what you want overriding some service.
I find that essential to implement
i.e. a global refresh zone strategy where a login component
triggers a 'logged in' event and where other components subscribe
to such an event because they have a zone that needs to refresh
to display a different price. It would also provide a much looser
connection between two less related components.
AFAIK, Tapestry, as it is now, doesn't support more than one handler
for the same event isntance.
Have you taken a look at MultiZoneUpdate? I guess it solves what you
want at least partly.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/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
