Re: close tag not found error in markup

2010-11-24 Thread andrea.castello
Basically, it is a (supposed) bug in version 1.4.13, something very similar to this https://issues.apache.org/jira/browse/WICKET-2620 Downgrading to 1.4.5 solved my issue. -- View this message in context:

Re: close tag not found error in markup

2010-11-24 Thread Martin Grigorov
Please create application that shows the problem. Zip it and attach it to a ticket in Jira. Thanks! On Wed, Nov 24, 2010 at 5:03 PM, andrea.castello a.castello.pronet...@gmail.com wrote: Basically, it is a (supposed) bug in version 1.4.13, something very similar to this

Re: close tag not found error in markup

2010-11-24 Thread Andrea Del Bene
Since version 1.4.6 DataTable HTML has changed to fix https://issues.apache.org/jira/browse/WICKET-2620. Component with id toolbar has been removed and that should cause the problem reported by Andrea. Until 1.4.5 /wicket:panel thead wicket:id=topToolbars wicket:container

Re: close tag not found error in markup

2010-11-24 Thread Ernesto Reinaldo Barreiro
Yes, I remember having to fix my own extension of DataTable when migrating between two 1.4.x versions. That might be the change you mention. Ernesto On Wed, Nov 24, 2010 at 5:55 PM, Andrea Del Bene adelb...@ciseonweb.it wrote: Since version 1.4.6 DataTable HTML has changed to fix

Re: close tag not found error in markup

2010-11-23 Thread Matthias Keller
Hi Andrea The error is: WicketMessage: close tag not found for tag: . Component: [MarkupContainer [Component id = toolbar]] I can't see a wicket:id=toolbar in your posted code, so the problem appears to be somewhere else on that page including the posted panel. Try to find that toolbar -

Re: close tag not found error in markup

2010-11-23 Thread andrea.castello
Sorry, I didn't paste all the code :( Here is the correct one where the span with is toolbar appears wicket:panel caption class=tableCaption /caption thead class=rowH /thead tbody tr wicket:id=rows td wicket:id=cells [cell] /td /tr /tbody tfoot

Re: close tag not found error in markup

2010-11-23 Thread andrea.castello
I am very sorry, but it seems like a portion of the code I paste is being stripped when I post it. This is the code that's nested inside the thead tag span wicket:id = topToolbars span wicket:id = toolbar / span Hope it's readable now (all those whitespaces are not in the original

Re: close tag not found error in markup

2010-11-23 Thread Andrea Del Bene
Hi Andrea, maybe have you just missed close tag for topToolbars component? In the last code snippet I see just one /span tag. I am very sorry, but it seems like a portion of the code I paste is being stripped when I post it. This is the code that's nested inside the thead tag span

Re: close tag not found error in markup

2010-11-23 Thread andrea.castello
Hi Andrea, thank you. In the original code the span tags are properly closed. Is it possible that in the 1.4.x versions nested span tags are not allowed (at least the ones with a wicket:id? Andrea Del Bene-2 wrote: Hi Andrea, maybe have you just missed close tag for topToolbars

Re: close tag not found error in markup

2010-11-23 Thread Andrea Del Bene
Is there any code inside toolbar? Is just an empty component? I am very sorry, but it seems like a portion of the code I paste is being stripped when I post it. This is the code that's nested inside the thead tag span wicket:id = topToolbars span wicket:id = toolbar / span

Re: close tag not found error in markup

2010-11-23 Thread Matthias Keller
Hi Andrea Make sure you remove that whitespace in span - that should be span and the same for / span - /span. Valid HTML must not contain whitespace there. Matt On 2010-11-23 11:35, andrea.castello wrote: I am very sorry, but it seems like a portion of the code I paste is being stripped

Re: close tag not found error in markup

2010-11-23 Thread andrea.castello
Matt, thank you, but original code has no whitespaces. To add, more the html markup worked perfectly in my app with Wicket 1.3.6 while all seems to break when I upgrade to Wicket 1.4.13 -- View this message in context: