Hi!
If you have:
<div wicket:id="listview-container">
<wicket:container wicket:id="list-view"/>
</div>
Which is laid out as:
...
panel.add((listviewContainer = new
WebMarkupContainer("listview-container")).setOutputMarkupId(true));
...
And in your ajax update you call:
...
target.addComponent(listviewContainer);
..
This should work.
**
Martin
2010/11/28 Wilhelmsen Tor Iver <[email protected]>:
> In my quest for a more portlet-oriented use of Wicket, I am trying an
> approach where you switch panels (by constructing new instances and
> repainting a "wrapper") within one Page. However, it seems that ListViews do
> not get repainted (no calls to populateItem()) in that scenario:
>
> 1) Initial rendering that does not use Ajax works fine.
> 2) An AjaxFallbackButton then switches to a second panel
> 3) Returning via an AjaxFallbackLink to a new instance of the first
> panel paints all components except the ListView items.
>
> Is there something I have forgotten? Would it make more sense to have all
> Panels in the Page at once and then just adjust visibility as needed?
>
> A quickstart can be found at http://dl.dropbox.com/u/11463405/listviewtest.zip
>
> Med vennlig hilsen
>
> TOR IVER WILHELMSEN
> Senior systemutvikler
> Arrive AS
> T (+47) 48 16 06 18
> E-post: [email protected]
> http://www.arrive.no
> http://servicedesk.arrive.no
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
