Hi, good news. I managed to remove Component.markupStreamPosition and some of the related stuff like Component.vaidateMarkupStream and Component.setRendering(). I didn't like it anyway (though it was me who introduced it). I'll check it in tonight.
The modifications have another advantage: resetMarkupStream(), resetMarkupStreams() and the related hierachy traversal are no longer needed as well which. Overall even the performance should improve a little bit. And because all tests are successful (and unchanged) the changes hopefully don't break anything. Juergen ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
