We use some kind of custom cascading behavior to achieve this
"pipeline of behaviors" effect. The first behavior does it thing,
calls the next in the sequence and so on. I don't think wicket
provides a standard mechanism for this. The main case of use we found
is for ajax form component updating behaviors that do something more,
as a country dropdown that must be validated and afterwards shows a
state dropdown. But all in all these are just marginal cases.
Regards,
Carlos
On 9/5/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
> I believe it will only fire the last added behavior.
>
> -Matej
>
> On 9/5/07, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote:
> > Dear Community,
> >
> > what happens if two or event behavior are added on the save event handler.
> >
> > I mean something like that
> >
> > Button b = new Button("the-button");l
> > b.add(new AjaxEventBehavior("onclick") {
> > protected void onEvent(AjaxRequestTarget target)
> > {
> > //DO THIS
> > }
> > });
> >
> >
> > b.add(new AjaxEventBehavior("onclick") {
> > protected void onEvent(AjaxRequestTarget target)
> > {
> > //DO THAT
> > }
> > });
> >
> >
> > Will be fired both? just the first? just the last?
> >
> > Thank to all.
> >
> > - P
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
