You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/08/27 15:46:54 UTC

[jira] Resolved: (WICKET-1185) Wrong message / parse error: "Expected close tag for "

     [ https://issues.apache.org/jira/browse/WICKET-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-1185.
----------------------------------------

    Resolution: Fixed

This is no problem more anymore.  In 1.5 the border body MUST be added at the right place within the hierarchy. And because the default case is to add to child to the border body, add() has been subclassed to call addToBorderBody().

The main point here is, that border no longer applies any magic to the component hierarchy vs. markup hierarchy anymore. And because of that, this error and the one mentioned by Eric no longer occurs.

But it's still the users responsibility to add the child to the right place (border or border body). While thinking about it ... since the markup is now available in the constructor, one could read the markup and automatically determine where to add the child too.

> Wrong message / parse error: "Expected close tag for <span wicket:id="column0">"
> --------------------------------------------------------------------------------
>
>                 Key: WICKET-1185
>                 URL: https://issues.apache.org/jira/browse/WICKET-1185
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-rc1, 1.4-RC2
>         Environment: Linux
>            Reporter: Johannes Schneider
>            Assignee: Juergen Donnerstag
>             Fix For: 1.5-M2
>
>         Attachments: bug-search.zip
>
>
> I get the message "Expected close tag for <span wicket:id="column0">". But the span is closed. So there exists an parse error or the error message is misleading.
> I am not a Wicket expert, so I think I have an error within my code and the error message is not good enough (for me).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.