Hi,
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:
Which is quite cryptic at the first glance.
Is there a way to handle the Wicket:container in the same way as other HTML
tags, or is this inevitable due to implementation limitations ?
Cheers.
--
View this message in context:
http://www.nabble.com/Inconsisting-Handling-of-id-mismatch-tp15908468p15908468.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
