have you tried it with trunk? -igor
On 8/31/07, Johannes Schneider <[EMAIL PROTECTED]> wrote: > > I don't use any AjaxFAllbackOrderByBorder or anything else in my code. > So I think there must be another trigger for the bug, too. > > > Johannes Schneider > > Jonas-21 wrote: > > 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 > >> > > > > -- > Johannes Schneider > Im Lindenwasen 15 > 72810 Gomaringen > > Fon +49 7072 9229972 > Fax +49 7072 509999 > Mobil +49 178 1364488 > > [EMAIL PROTECTED] > http://www.johannes-schneider.info > >
