> So this special component is designed to be aware of children components
> only at the rendering time ( working with the markupStream ) and not at the
> pre-rendering. As the ListView depends on pre-rendering logic, add an
> transparent resolved component in ajax request target has no effect beca
When an transparent resolved component is rendered, it is able to correctly
resolve any wicket:id in the inner html object because it delegates the
Component#get to its parent, and it is able to know who are its children
components traversing the html at at the markupStream object.
So this special
Transparent container probably doesn't exist/have an id so yes.. but I
guess this could be "fixed"/automated in wicket.
**
Martin
2010/11/29 Wilhelmsen Tor Iver :
>> wicket:enclosure is not present if not visible (from browser
>> perspective). So it cannot be repainted.
>
> I think we are talking
> wicket:enclosure is not present if not visible (from browser
> perspective). So it cannot be repainted.
I think we are talking past each other: It was just an example of something
that is a transparent container to a Wicket developer, though it is implemented
using IComponentResolver instead o
wicket:enclosure is not present if not visible (from browser
perspective). So it cannot be repainted.
http://apache-wicket.1842946.n4.nabble.com/Wicket-ajax-enabled-enclosures-td3033370.html
2010/11/29 Wilhelmsen Tor Iver :
>> I don't know what you mean with transparent but ofcourse you cannot
>>
> I don't know what you mean with transparent but ofcourse you cannot
> repaint invisible things.
A transparent container is one that appears in the markup and in the code but
which returns true for isTransparentResolver(). It's not "invisible" but is not
part of the explicit hierarchy. An examp
I don't know what you mean with transparent but ofcourse you cannot
repaint invisible things.
**
Martin
2010/11/29 Wilhelmsen Tor Iver :
>>
>>
>>
>>
>> Which is laid out as:
>> ...
>> panel.add((listviewContainer = new
>> WebMarkupContainer("listview-container")).setOutputMarkupId(true));
>>
>
>
>
>
> Which is laid out as:
> ...
> panel.add((listviewContainer = new
> WebMarkupContainer("listview-container")).setOutputMarkupId(true));
> ...
This is almost what I have (in the Page), except the outermost one is
transparent; in the "real" project the only reason is to wrap both a
Hi!
If you have:
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 Iv
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
10 matches
Mail list logo
