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
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
Since it is illegal, I think Wicket should be throwing an Exception instead of yielding an OutOfMemoryError
--AndrewOn 11/14/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
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
Agreed. Would you please of a bug for it. Thanks
Juergen
On 11/14/05, Andrew Berman [EMAIL PROTECTED] wrote:
Since it is illegal, I think Wicket should be throwing an Exception instead
of yielding an OutOfMemoryError
--Andrew
On 11/14/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
https://sourceforge.net/tracker/index.php?func=detailaid=1356696group_id=119783atid=684975
On 11/14/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Agreed. Would you please of a bug for it. ThanksJuergenOn 11/14/05, Andrew Berman [EMAIL PROTECTED] wrote: Since it is illegal, I think Wicket should
