[ http://issues.apache.org/jira/browse/TAPESTRY-1168?page=all ]
Jesse Kuhnert resolved TAPESTRY-1168.
-------------------------------------
Fix Version/s: 4.1.1
Resolution: Fixed
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..)
> Update of nested component causes it to lose its @EventListener
> ---------------------------------------------------------------
>
> Key: TAPESTRY-1168
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1168
> Project: Tapestry
> Issue Type: Bug
> Components: Annotations
> Affects Versions: 4.1.1
> Environment: Windows XP SP2
> Java JDK 1.5 Update 9
> Tapestry 4.1.1-20061126.014659-1
> Reporter: Mark Reynolds
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
> Attachments: mintap_3.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
