Alex: We implemented a subclass of Form that has some sophisticated validation and customized feedback panels built-in. This form automatically "instruments" its fields with an ajax validating behavior. But sometimes -not that often- a field needs to ajax-do a bit more than just being validated, so this extra behavior is passed as a handler that knows how to react onSubmit and onError. Well, to the point: at first we implemented this extra behavior as sort of chained behavior, but then, as we found out that this generality was adding extra complexity and didn't really pay off, we moved out to a simpler schema with a handler implementing an onSubmit/onError barebones interface, to which the only behavior delegates at last. So now there is only one behavior and nothing that resembles a chain. In part, that's the reason why I feel that such a functionality is out of the scope of a general framework/toolkit as wicket is.
Regards, Carlos On 9/6/07, Alex Objelean <[EMAIL PROTECTED]> wrote: > > I am curious, what is your use case for chaining behaviors? > I think that if you have two things that you want to chain, then chain them > in the same handler, or use decorator to add the client-side code. > > Alex > > > paolo di tommaso wrote: > > > > Carlos, > > > > Can you provide an example of your custom implementation of chained > > behaviour? > > > > > > Thanks, Paolo > > > > > > On 9/6/07, Carlos Pita <[EMAIL PROTECTED]> wrote: > >> > >> > Currently people will have to build it in themselves like you did. We > >> > can investigate whether this can be improved for future versions, but > >> > >> From my own experience I wouldn't say that wicket should support this. > >> It's too easy to write it yourself just to fit your specific needs, > >> and otoh seems difficult to predict and support a significant number > >> of possible use cases in a general way that keeps everyone happy, as > >> you remarked. > >> > >> Regards, > >> Carlos > >> > >> > > >> > Eelco > >> > > >> > --------------------------------------------------------------------- > >> > 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] > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Twice-Behavior-on-the-same-event-handler-%28wicket-1.2.x%29-tf4386351.html#a12518265 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
