icket i tend to call
methods on dependent components from ajax event handlers. Is this a good
approach - (it atleast dont feel so good)?
--
View this message in context:
http://www.nabble.com/Good-wicket-patterns-tp17139005p17139005.html
Sent from the Wicket - User mailing list a
> Ajax
>
> 3. Now im working with more Ajax. What is a good inter component
> communication scheme? Swing has its listeners, but in wicket i tend to call
> methods on dependent components from ajax event handlers. Is this a good
> approach - (it atleast dont feel so good)?
I try to have my co
e.g.
public class AjaxEvent
{
private Set listeners = new HashSet();
public void register(Component listener)
{
listeners.add(listener);
}
public void fire(AjaxRequestTarget request)
{
for (Component listener : liste
You could have a look at the "broadcaster" that is discussed in
https://issues.apache.org/jira/browse/WICKET-1312
The solution that is proposed there uses a visitor instead of
registration. That has the advantage that you don't have to
_unregister_ at the appropriate time. Because Wicket does no
> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA
> 94952-3329 +1 (707) 773-4646
> -
ith more Ajax. What is a good inter component
> communication scheme? Swing has its listeners, but in wicket i tend to call
> methods on dependent components from ajax event handlers. Is this a good
> approach - (it atleast dont feel so good)?
>
>
> --
> View this message in cont
its listeners, but in wicket i tend to
>> call
>> methods on dependent components from ajax event handlers. Is this a good
>> approach - (it atleast dont feel so good)?
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Good-wicket-
bel(...,obj.toString)
> >> take
> >> lists-of-objects. Or, is more advisable to keep a component's model
> >> contained within itself? I have yet to find a good practice here.
> >>
> >> Ajax
> >>
> >> 3. Now im working with m
