Jesse Kuhnert wrote:
I don't think "onClick" will be a valid js event name to listen to. In
this instance it has to be "onclick" .
Thanks, it could be a reason (I was changing several things at once
trying to fix it so I'm only 90% sure that that's it ;-)).
And I've noticed that even when @EventListener is added to one component
of a page when it's clicked the whole "rendering" is taking place. By
rendering I mean that pageBeginRender() method of the enclosing page is
being called. As an effect - whole logic responsible for pulling data
for whole page from underlying DB is being called...
So questions are:
1. Is there ANY place where behaviour of @EventListener (lifecycle of
involved components) is described?
2. It seems like a bad optimization if logic for whole page and its
component tree is being called, when I just want to update one widget on
the page... How can I optimize it?
TIA,
Wojtek
----------------------------------------------------------------------
Masz plan? Potrzebujesz motywacji ?
wejdz na >>> http://link.interia.pl/f1a40
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
