in 1.5 AjaxLink adds its AjaxEventBehavior in its #onInitialize()
method. that's why it comes second
You'll have to override onInitialize and add your behavior there
On Wed, Sep 21, 2011 at 4:52 PM, Marcel Hoerr <marcel.ho...@gmx.de> wrote:
> hey guys,
>
> i have a problem with an AttributeModifer and an AjaxLink in wicket 1.5. we
> havea custom AttributeModifier ("onclick") which basicly adds a javascript
> confirm to the given component (Button or in this case an AjaxLink).
>
> in wicket 1.4 the AttributeModifier is added after the AjaxEventBehavior (and
> its "onclick") of the AjaxLink, in wicket 1.5 the AttributeModifier comes
> first and gets overriden by the AjaxEventBehavior of the AjaxLink.
>
> is this a bug or a feature?
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
