Bugs item #1457509, was opened at 2006-03-24 04:24
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1457509&group_id=119783

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: 1.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Geoff (mrbythatmuch)
Assigned to: Nobody/Anonymous (nobody)
Summary: infinite loop

Initial Comment:
Add this as a new one because 
[ wicket-Bugs-1442757 ] Ajax errors in a Border
was closed although the abilty to be trapped in an 
infinite loop
   while (markupStream == null)
remains.

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 match 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???


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1457509&group_id=119783


-------------------------------------------------------
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

Reply via email to