You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Funk (JIRA)" <ji...@apache.org> on 2009/05/11 13:37:46 UTC

[jira] Updated: (WICKET-713) AbstractAjaxBehavior can not be reused.

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

Martin Funk updated WICKET-713:
-------------------------------

    Attachment: patch-mf-713.diff

based on Brunos patch I gave my try on this subject.

Rethinking this issue, brought to me that not beeing able to readd an AbstractAjaxBehavior is not the real issue here. They are indeed verry cheap to recreate. But its the lack of the unBind method in the interface and its (not) support by component. That way noone can be notified when the behavior is removed.

> AbstractAjaxBehavior can not be reused.
> ---------------------------------------
>
>                 Key: WICKET-713
>                 URL: https://issues.apache.org/jira/browse/WICKET-713
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>            Reporter: Martin Funk
>             Fix For: 1.5-M1
>
>         Attachments: patch-713.diff, patch-mf-713.diff
>
>
> AbstractAjaxBehavior is receiving a Component upon bind, this is keept even when the Behavior is removed from the Component
> so if the Behavior is added again it throws a 
> 				IllegalStateException("this kind of handler cannot be attached to "
> 					+ "multiple components; it is already attached to component " + this.component
> 					+ ", but component " + hostComponent + " wants to be attached too");

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