Yes it is illegal. It was in the past as well, but we didn't check it. In order to support per-component re-render there has to be a 1:1 match.
Juergen On 11/14/05, Andrew Berman <[EMAIL PROTECTED]> wrote: > I just did another test and did this: > > <div wicket:id="pagingNavigator"></div> > <div wicket:id="pagingNavigator"></div> > .... > > I put them right after each other. Now the page infinitely builds > PagingNavigators and the screen just keeps going. It just keeps going and > going..... > > --Andrew > > > > On 11/14/05, Andrew Berman <[EMAIL PROTECTED]> wrote: > > Ok, when using Wicket 1.1, I was able to do this: > > > > <div wicket:id="pagingNavigator"></div> > > .... > > <div wicket:id="pagingNavigator"></div> > > > > This allowed me to have the paging navigator at the top and bottom of the > data. > > > > However, when using HEAD, I get java.lang.OutOfMemoryError: Java heap > space. It works if I just have one PagingNavigator. Is it illegal to have > an element with the same wicket:id on one page now? If so, why? > > > > Thanks, > > > > Andrew > > > > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
