It's that way to emphasize that an AbstractAjaxBehavior can be bound to
a single component only. Why change it?
Sven
On 08/01/2013 12:25 PM, Martin Grigorov wrote:
Hi,
Is there any reason why AbstractAjaxBehavior#onComponentTag(Component,
ComponentTag) is final and delegates to "#onComponentTag(ComponentTag)"
(note the missing 'component' parameter) ?
The idea is to use #getComponent() if access to the bound Component is
needed inside #onComponentTag(ComponentTag). But I don't see why we hide
the component this way from the user.
Any objections to make the first non-final and deprecate the second in
Wicket 7.x ?
