As suggested on this list I'm using an IComponentResolver to auto-add
'optional' components to my Wicket pages.
Everything works fine until the request cycle cleans up:
java.lang.ArrayIndexOutOfBoundsException: 5
at wicket.MarkupContainer.children_get(MarkupContainer.java:998)
at wicket.MarkupContainer.internalEndRequest(MarkupContainer.java:344)
at wicket.request.target.component.BookmarkablePageRequestTarget.cleanUp(.)
at ...
The reason for this can be found in HtmlHeaderContainer:
It removes itself from its parent in #onEndRequest(), thus interfering with the
iteration over the children in MarkupContainer#internalEndRequest().
Usually this poses no problem because HtmlHeaderContainer is the last child.
But in my case auto-added additional components are positioned at the end of
the children array.
So my question:
Could we reverse the iteration over the children in
MarkupContainer#internalEndRequest():
>final int size = children_size();
>for (int i = size - 1; i >= 0; i--)
>{
>...
>}
Sven
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
