[jira] Updated: (TAPESTRY-2092) EventListener in components that get included more than once in a page aren't triggered

["Andreas Andreou (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Andreou updated TAPESTRY-2092:
--------------------------------------

    Attachment: tap-2092.zip

a maven project to reproduce this

> EventListener in components that get included more than once in a page aren't triggered 
> ----------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2092
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2092
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Annotations, Framework
>    Affects Versions: 4.1.3
>            Reporter: Andreas Andreou
>         Attachments: tap-2092.zip
>
>
> In a simple component (@Selector) that has a PropertySelection (named data) and this:
>     @EventListener(targets="data", events="onchange")
>     public void doSelect() { System.out.println("Selected: " + getValue()); }
> and in a page that includes this let's say 3 times:
> <form jwcid="@Form">
>    <span jwcid="@Selector"/>
>    <span jwcid="@Selector"/>
>    <span jwcid="@Selector"/>
> </form>
> Only the first selector triggers its listener + i dont see javascript that would bind the onchange event of the other ones.
> Is this something trivial to fix? 
> Is this a known limitation of the EventListener annotation? 
> Would an EventListener component make things easier in such cases?
> (btw, TAPESTRY-2070 could be similar)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org