[ https://issues.apache.org/jira/browse/WICKET-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029902#comment-13029902 ]
Martin Grigorov commented on WICKET-3673: ----------------------------------------- There is some work on this at https://github.com/ivaynberg/wicket/tree/component-queuing. AFAIR there is no other ticket, but I may be wrong. > A little heuristic for "Unable to find component" exception > ----------------------------------------------------------- > > Key: WICKET-3673 > URL: https://issues.apache.org/jira/browse/WICKET-3673 > Project: Wicket > Issue Type: Improvement > Components: wicket-core > Affects Versions: 1.4.17 > Reporter: Ondra Žižka > Fix For: 1.6.0 > > > Sometimes it's easy to get lost in the structure of a page / component. > This leads to a situation when the component is correctly created in HTML and > code, but at different level, like > {code} > form.add(new Label("foo", ...)) > add(new Label("bar", ...)) > {code} > instead of > {code} > form.add(new Label("foo", ...)) > .add(new Label("bar", ...)) > {code} > I suggest that the component map could be searched for components with the ID > which is not found where expected, and if such ID would be found at different > level, it would advice the user to check whether the structure is ok instead > of simply stating "not found". > Since this is the most common cause of that exception (from my experience), > I think this could save users from loosing time on checking typos etc, when > they are out of caffeine and start doing mistakes at the end of the day :) > Thanks for considering. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira