[WICKET-4959] Notify behaviors when a component is removed from the tree

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.4.0
• Fix Version/s: 6.5.0
• Component/s: wicket-extensions
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Paul
• Created: 09/Jan/13 10:51
• Updated: 23/Jan/18 20:10
• Resolved: 18/Jan/13 08:04

Description

I use a AjaxTabbedPanel on my page and run into the following problem:

If there is an Behavior (AjaxSelfUpdatingTimer or AbstractAjaxTimerBehavior) attached to one of the panels and the panel is replaced by another panel, the AjaxBehavior is not properly removed and deactivated. After the idle-duration the JS calls in and Wicket throws an exception due to the missing behavior.

Stacktrace:
ERROR - DefaultExceptionMapper - Unexpected error occurred
org.apache.wicket.behavior.InvalidBehaviorIdException: Cannot find behavior with id '0' on component 'org.apache.wicket.markup.html.panel.EmptyPanel:tabs:panel' in page '[Page class = com.wicket.HomePage, id = 0, render count = 4]'. Perhaps the behavior did not properly implement getStatelessHint() and returned 'true' to indicate that it is stateless instead of returning 'false' to indicate that it is stateful.
at org.apache.wicket.Behaviors.getBehaviorById(Behaviors.java:303)
at org.apache.wicket.Component.getBehaviorById(Component.java:4483)
at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:246)
at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
...

I attached a quickstart showing the problem. Simply take a look at second tab and then go back to the first tab and you run into this problem.

There is a workaround for this: If you attach the behavior to a component of the panel (i.e. the clock) this error doesn't occur.

Issue Links

• breaks: WICKET-5104 AjaxSelfUpdatingTimerBehavior in hidden component in ModalWindow causes Ajax Response Error
• is related to: WICKET-6523 Two AbstractAjaxTimerBehaviors on same component timeId conflict
• relates to: WICKET-5464 AbstractAjaxTimerBehavior does not work in combination with Wizards