[
https://issues.apache.org/jira/browse/WICKET-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604770#action_12604770
]
Martin Funk commented on WICKET-713:
------------------------------------
it still lives look at:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2-examples/src/main/java/wicket/contrib/examples/gmap/listen/HomePage.java
(in the lower third, or search for
'https://issues.apache.org/jira/browse/WICKET-713')
I got a counter question on this one.
IBehavior may be added to Component.
Component calls IBehaviors bind while adding it.
IBehavior may be removed from Component,
But why is there is no unbind callback?
And why may the removed IBehavior never be readded to any Component again?
This way Behaviors feel like half baked Components.
Though there are signs in the code, esp. when managing the versions of a
Component, that an onUnBind in IBehavior might have unwanted side effects.
> 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.4-M3
>
>
> 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.
