[Wicket-user] Using the same PagingNavigator on the same page yields OutOfMemoryError

[Andrew Berman]

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