dashorst opened a new issue, #1957:
URL: https://github.com/apache/wicket/issues/1957
When a component that was invisible at first render (and so has no markup in
the response) is later added to an Ajax update, rendering fails with:
```
org.apache.wicket.markup.MarkupNotFoundException: Markup not found for
Component: [FencedFeedbackPanel [Component id = feedback]]
```
The message gives the component's class and id, but not the page or the
component's path, so in a large application it is hard to tell which of many
`feedback` components failed, and why.
## Where
`wicket-core/src/main/java/org/apache/wicket/Component.java`,
`internalRender()`, where the exception is thrown, and the other places in
`Component` and `MarkupContainer` that throw `MarkupNotFoundException` or
`MarkupException("Markup not found…")`.
## Done when
- The message includes the page class and the component's page-relative
path. Where it's cheap to tell, add a hint for the common cause (a component
added to an Ajax update whose parent's markup doesn't contain it).
- Tests that assert on the new message in `wicket-core-tests`.
## Background
Originally reported as
[WICKET-6538](https://issues.apache.org/jira/browse/WICKET-6538) (Wicket 7.9).
Another user agreed that the page name would help.
---
Part of #1945. This issue is meant for a first contribution to Wicket. To
work on it, leave a comment so others know; a claim without a pull request
lapses after two weeks. Questions are welcome, here on the issue or on
[email protected]. Start your branch from `master`, and see [Send a pull
request to
Wicket](https://wicket.apache.org/contribute/wicket-pull-request.html) for
building and testing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]