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 2008/12/21 11:06:44 UTC

[jira] Resolved: (WICKET-1750) Inconsisting Handling of id mismatch on wicket:container

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

Juergen Donnerstag resolved WICKET-1750.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4-RC2
         Assignee: Juergen Donnerstag

error message improved. Thanks

> Inconsisting Handling of id mismatch on wicket:container
> --------------------------------------------------------
>
>                 Key: WICKET-1750
>                 URL: https://issues.apache.org/jira/browse/WICKET-1750
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M2
>            Reporter: Marat Radchenko
>            Assignee: Juergen Donnerstag
>             Fix For: 1.4-RC2
>
>
>   Given this simple case:
> public class Home extends WebPage {
>     public Home() {
>         add(new EmptyPanel("test"));
>     }
> }
> and the following HTML page:
> <span wicket:id='test2'/>
> Please notice that the ids do not match.
> Executing this app will give the following Exception:
> WicketMessage: Unable to find component with id 'test2' in [Page class =
> com.myapp.wicket.Home, id = 0, version = 0]. This means that you declared
> wicket:id=test2 in your markup, but that you either did not add the
> component to your page at all, or that the hierarchy does not match.
> Whereas when using a wicket:container instead of a HTML tag, like this:
> <wicket:container wicket:id='test2'/>
> And when the ids doesn't match, Wicket throws the following exception:
> WicketMessage: Failed to handle: <wicket:container wicket:id='test2'/>
> Which is quite cryptic at the first glance.
> Original: http://mail-archives.apache.org/mod_mbox/wicket-dev/200803.mbox/%3c15908468.post@talk.nabble.com%3e
> We ran across same problem too.

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