Wicket and complex Ajax scenarios

Question

When a screen has multiple interacting Ajax controls and you want to control the visibility of components to react to these controls (so that you only display what makes sen

Answer 1

I currently use some sort of modified Observer-Pattern to simulate an event-bus in Wicket 1.4.

My Pages act as an observable observer since my components don't know each other and are reused in different combinations across multiple pages. Whenever one component receives an Ajax-event that could affect other components as well, it calls a method on it's page with an event-object and the ajax-target. The page calls a similar method on all components which have registered themselves for this kind of event and each component can decide, on the base of the supplied event-object if and how it has to react and can attach itself to the target.

The same can be archived by using the wicket visitor. I don't know which one is better, but I think that's mainly a matter of taste.