Or maybe just have a "sortYourSelfOut" method that gets called on all components after any changes but before the the wicket response life cycle? Any existing Wicket methods fit this? onBeforeRender? Needs to get called on _all_ components even for Ajax request...
Sorry for talking to myself. Sam Hough wrote: > > Has anybody used something like javax.swing.ListModel.addListDataListener > or java.util.Observable to setup a nice way for components to respond to > changes in other components? > > My use case is that I have a "basket" of items a user has selected. While > they are searching/browsing if an item already in the basket appears again > I want it to be disabled/greyed out. With hand coding that is a bit ugly > and seems like a candidate for some sort listening to changes in another > component. > -- View this message in context: http://www.nabble.com/Inter-component-events--tf4508127.html#a12857280 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
