or as simple as this:ListView lv=new ListView(...);add(lv);add(new PagingNavigator("header", lv));add(new PagingNavigator("footer", lv));
-IgorOn 6/26/06, Stephane Bailliez <[EMAIL PROTECTED]> wrote:
Igor Vaynberg wrote:> no, this was possible in 1.1 but in 1.2 due to various reasons,> including aj
Igor Vaynberg wrote:
> no, this was possible in 1.1 but in 1.2 due to various reasons,
> including ajax support, we no longer support that feature.
>
> so if you want to wrap the table create the header and footer that both
> reference the same model that way they will always stay in sync.
Yes
No it is not possible to have one component instance included twice.
This would mean a problem with determining what the parent is of the
component, and where Wicket would attach the component in the final
markup. This would also mean duplicating the exact markup.
IIRC, when you create two paging
no, this was possible in 1.1 but in 1.2 due to various reasons, including ajax support, we no longer support that feature.so if you want to wrap the table create the header and footer that both reference the same model that way they will always stay in sync.
-IgorOn 6/26/06, Stephane Bailliez <[EMA
Is it possible to have multiple rendering of the same component per page
with the same wicket:id ?
It does not look so as it complains that "xxx has the same wicket:id as
another component already added at the same level"
The idea was to wrap a table around a header and footer navigator and as
