Thanks Howard,
But if my event from A is seen as "FromB" in component C, all events
from components B are melted and one can't handle a specific event !
Shouldn't we be able to differ events from their id or at least from
their type from Form, Links, ... ?
Howard Lewis Ship a écrit :
This simply isn't how its done. Once an event bubbles up from
component A to container B to container C, it will appear as "FromB"
in the methods of C. Is that clear? This is explicitly to enforce
that component implementations are private to the component, such that
a component (A or B) may change its structure, including the ids of
embedded components, without requiring changes outside the component.
On Feb 16, 2008 6:24 AM, Steph <[EMAIL PROTECTED]> wrote:
I've achieved to handle the event of my component in its container by
changing the event handler like this :
@OnEvent(component="the_name_of_my_component_in_the_container")
So i can handle now all the events bubbling from my component.
But what if i just want to handle the event of my 'detaillink' in the
component ?
I've tried something like that :
@OnEvent(component="the_name_of_my_component_in_the_container.detaillink")
without success ...
Any advice is welcome
Stephane
Steph a écrit :
Hi,
I've got a strange behavior in event bubbling ...
I have an actionlink in a component :
<t:actionlink t:id="detaillink" context="${id}" class="highlight">Show
details ...</t:actionlink>
If I write an event handler in the component, the event is handle
correctly :
@OnEvent (component="detaillink")
Object detailLink(Long id) {
... do the handling based on the id and return a page to redirect
to ...
}
But if i move this handler (with no modifications) from the component
to the page that includes the component, the handler is never called ...
According to the documentation, i thought that event bubbling implies
that the handlers of the container of my component should be parsed ...
Thanks in advance for any advice.
Stephane
