Tapestry
  1. Tapestry
  2. TAPESTRY-1168

Update of nested component causes it to lose its @EventListener

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.1
    • Component/s: Annotations
    • Labels:
      None
    • Environment:
      Windows XP SP2
      Java JDK 1.5 Update 9
      Tapestry 4.1.1-20061126.014659-1

      Description

      See attached project to replicate issue.

      When I call .updateComponent() on a @Any component that contains a PropertySelection tied to an @EventListener, the updated PropertySelection appears to lose its event binding.

      1. mintap_3.zip
        10 kB
        Mark Reynolds

        Activity

        Hide
        Mark Reynolds added a comment -

        Looks great! Thanks so much, Jesse.

        Show
        Mark Reynolds added a comment - Looks great! Thanks so much, Jesse.
        Hide
        Jesse Kuhnert added a comment -

        Even though it doesn't make the bug any less valid , I thought I should point out that all of the example apps you've submitted use "elements=''" instead of targets="". Elements are when you are targeting strict generic html elements, target is for real bonafied components. (Like any/propertyselection/etc..)

        Show
        Jesse Kuhnert added a comment - Even though it doesn't make the bug any less valid , I thought I should point out that all of the example apps you've submitted use "elements=''" instead of targets="". Elements are when you are targeting strict generic html elements, target is for real bonafied components. (Like any/propertyselection/etc..)

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Mark Reynolds
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development