I've been able to reproduce the problem with a these few classes: http://www.nabble.com/file/p12409279/Expected_close_tag.zip Expected_close_tag.zip
It seems to be caused by the problem that BorderBodyResolver warns about: Unlike OrderByBorder, AjaxFallbackOrderByBorder doesn't add the BorderBodyContainer so it fits the markup. Now, if AjaxFallbackOrderByBorder is wrapped in another Border (as in my attached example), we don't get that nice log message, instead we get that 'Expected close tag for ...' message. So, it seems https://issues.apache.org/jira/browse/WICKET-166 actually IS relevant for wicket 1.3.0. (Of course the fix looks now different because of the api change) cheers, Jonas igor.vaynberg wrote: > > hmm, if you could create a quickstart for this it would be very helpful. > > -igor > -- View this message in context: http://www.nabble.com/Regression-in-1.3.0-beta3%28-%29-tf4346638.html#a12409279 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
