Hello,
I decided to take another look at this problem and noticed that AJAX-based
refreshing of a page with a DataView changes the path of the DataView's
first element. For example, when the page is first rendered, the path of the
first row in the DataView is referrals:1. After the DataView is
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
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.nowrote:
I remember reading somewhere that using
Any thoughts on this?
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.)
Thanks
On Mon, Sep 20, 2010 at
2010/9/21 Alec Swan alecs...@gmail.com
Any thoughts on this?
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
Hello,
I have a page which contains a DropDownChoice menu and a table. The
menu has AjaxFormComponentUpdatingBehavior which causes the table to
refresh. The page is actually working correctly, but I am having
problems with a test.
The test does the following:
1. Renders the page
2. Verifies that
