I have experienced the same error.
It is because the border is not being added correctly. But it WILL happen
when you added it as described in the wiki
http://www.wicket-wiki.org.uk/wiki/index.php/Migrate-1.2
The page renders correctly however when an ajax request is send the markup
id does not matching the component map id. Then an infinite loop occurs in
public abstract class Component implements Serializable
private final MarkupStream initializeMarkupStream()
....
while (markupStream == null)
Presently my work around is to have my applications base page class from
which all pages are entered from include not just
border = new foo.Border("border");
border.setTransparentResolver(true);
super.add(border);
as show in the wicket but I override the add with
public MarkupContainer add(Component arg0) {
if(border==null)
return super.add(arg0);
else{
border.add(arg0);
return this;
}
}
The infinite loop needs to be resolved/trapped and I'm not sure that
wicket.markup.html.border.Border is behaving as expected since my override
with the add is part of how the border worked in 1.1 which perhaps
border.setTransparentResolver(true); was supposed to change/handle???
--
View this message in context:
http://www.nabble.com/Fwd%3A-wicket-Bugs-1442757-Ajax-errors-in-a-Border-t1241784.html#a3565528
Sent from the Wicket - User forum at Nabble.com.
-------------------------------------------------------
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-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
