Hi Martin, Many thanks for your answer.
> > -Could this be prevented by wicket somehow? > > > > I do not see how. > If the component is in the tree then the visitor will see it and add it to > ART. > I mean component is added ==> even if not visible check if markup is there (early complain about the problem). Real problem was hidden til ART make it appear. > > > - If not, at least provide a more meaningful/helpful error message (e.g > > context in which markup is not found)? > > > > Definitely! > Wicket can/should log the component path instead of just the component id. > This will make it much easier to debug the problem. > Yes that would be great. Should I create an ISSUE for that? Maybe + PR :-) > > > > > > > > > > > > On Thu, Feb 8, 2018 at 6:44 AM, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > > Hi, > > > > > > On one application we are getting sporadic errors like > > > > > > org.apache.wicket.markup.MarkupNotFoundException: Markup not found for > > > Component: [FencedFeedbackPanel [Component id = feedback]] > > > at org.apache.wicket.Component.internalRender(Component.java:2348) > > > at org.apache.wicket.Component.render(Component.java:2308) > > > at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent( > > > XmlPartialPageUpdate.java:119) > > > at org.apache.wicket.page.PartialPageUpdate.writeComponents( > > > PartialPageUpdate.java:248) > > > at org.apache.wicket.page.PartialPageUpdate.writeTo( > > > PartialPageUpdate.java:161) > > > at org.apache.wicket.ajax.AjaxRequestHandler.respond( > > > AjaxRequestHandler.java:358) > > > at org.apache.wicket.request.cycle.RequestCycle$ > HandlerExecutor.respond( > > > RequestCycle.java:895) > > > at org.apache.wicket.request.RequestHandlerStack.execute( > > > RequestHandlerStack.java:64) > > > at org.apache.wicket.request.RequestHandlerStack.execute( > > > RequestHandlerStack.java:97) > > > a > > > > > > Error is not always produced. I have been checking JIRA and the only > > thing > > > I have found that looks similar is > > > > > > https://issues.apache.org/jira/browse/WICKET-6027 > > > > > > But we are on 7.4 and it does not seem to be the same combination of > > > factors. If we could avoid going to newer versions and find why and > > > "workaround" that would be ideal. > > > > > > Any hints? Related know issues? > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
