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
Would it make sense to have a behavior that was implemented as a Chain
of Responsibility
http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern
Then it would just be a matter of adding that behavior to your component.
On 9/6/07, Alex Objelean [EMAIL PROTECTED] wrote:
I am curious, what
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
the problem with this stuff is that there is no single pattern that will
work
sometimes you want a chain where if a link fails the chain shortcircuits
other times you dont want the shortcircuit
sometimes you care about the order, other times you do not
there are many variations of this and they
On 9/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
the problem with this stuff is that there is no single pattern that will
work
sometimes you want a chain where if a link fails the chain shortcircuits
other times you dont want the shortcircuit
sometimes you care about the order, other times
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
