Well, the table gets correctly refreshed through an AJAX event, it's just that WicketTester can't find any rows in the table after that.
Is this a known WicketTester bug? On Wed, Sep 22, 2010 at 12:41 AM, Wilhelmsen Tor Iver <toriv...@arrive.no>wrote: > > I remember reading somewhere that using AJAX to refresh a component > > generated using "repeater" may cause some problems. Is this what I am > > against here with WicketTester? (Keep in mind that the table does get > > refreshed correctly in production.) > > Repeaters are special in the sense that they take their markup and > repeatedly use it, thus there is not one "repeater" element in the DOM. To > use a repeater with Ajax you need to wrap it in e.g. a WebMarkupContainer > and then repaint that with Ajax. > > - Tor Iver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
