Hi Chris,
I don't see a reason why your challenge shouldn't work.
What happens if you reload the page (F5) after adding via Ajax? Do the
missing cells show up?
Have fun
Sven
Am 18.06.2018 um 21:26 schrieb Chris Colman:
I have an interesting List related challenge - I'm using RefreshingView
and having trouble when adding new rows.
The problem is a repeating view within a repeating view
i.e.
I have a table with two columns.
Each row is populated by the RefreshingView.
The cells in the right hand column contain their own wicket panel which
contains a sub table with a single column table.
This sub table is populated via an inner RefreshingView.
Eg.,
Col 1 | Col 2
----------------------
Name1 | Panel with sub table
| Label 1.1
| Label 1.2
| Label 1.3
----------------------
Name 2 | Panel with sub table
| Label 2.1
| Label 2.2
-----------------------
Etc.
Both the outer RefreshingView and the inner view are wrapped in
WebMarkupContainers.
The outer refreshing view and each inner refreshing view render
perfectly when the whole page is rendered but I have an Ajax button that
allows users to dynamically add new rows to the top level table and the
new entries don't render correctly.
I add the outer RefreshingList's (containing the outer table)
WebMarkupContainer to the Ajax target and Column 1 displays fine but
column 2 is left blank for new entries.
Eg., if user adds a new row to above by clicking the Ajax button they
see:
Col 1 | Col 2
----------------------
Name1 | Panel with sub table
| Label 1.1
| Label 1.2
| Label 1.3
----------------------
Name 2 | Panel with sub table
| Label 2.1
| Label 2.2
-----------------------
Name 3 |
-----------------------
I have set reuse strategy for both inner and outer RefressingViewS via:
setItemReuseStrategy(ReuseIfModelsEqualStrategy.getInstance());
Debugging reveals that a new inner panel is constructed and its
onInitialize method is called, however, the populateItem method is never
called for it's inner RefreshingView.
Is there something I've missed to cause the populateItem method to be
called to populate the new row fully or am I pushing the limits of what
the RefreshingView was designed for by nesting them like this?
-----Original Message-----
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, 25 May 2018 8:12 AM
To: users@wicket.apache.org
Subject: Re: ListView
On Thu, May 24, 2018 at 2:01 PM, JavaTraveler <meteor.ei...@gmail.com>
wrote:
Quickstart ?
a mini application showing the problem
https://wicket.apache.org/start/quickstart.html
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-
f1842947.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
