Description
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
form.add(new Label("foo", ...)) add(new Label("bar", ...))
instead of
form.add(new Label("foo", ...)) .add(new Label("bar", ...))
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.
Attachments
Issue Links
- is related to
-
WICKET-3335 Component Queueing (extract hierarchy information from markup)
- Resolved