On 6/25/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
What are the side effects?

Jonathan had problems:
http://www.nabble.com/Unable-to-find-the-markup-for-the-component-tf3976741.html
and
the project I'm working on got some exceptions from the test site this
morning as well. For instance:

org.apache.wicket.WicketRuntimeException: Unable to find the markup
for the component. That may be due to transparent containers or
components implementing IComponentResolver: [MarkupContainer
[Component id = text, page =
ts4.web.wicket.page.workspace.ComponentPage, path =
1:content:reply-form:form:text.KeepAliveTextArea, isVisible = true,
isVersioned = false]]
              at
org.apache.wicket.MarkupFragmentFinder.find(MarkupFragmentFinder.java:111)
              at
org.apache.wicket.Component.getMarkupAttributes(Component.java:1176)
              at org.apache.wicket.Component.getMarkupId(Component.java:1211)
              at
org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getPreconditionScript(AbstractAjaxTimerBehavior.java:96)
              at
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.generateCallbackScript(AbstractDefaultAjaxBehavior.java:161)
              at
org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getCallbackScript(AbstractAjaxTimerBehavior.java:84)
              at
org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getJsTimeoutCall(AbstractAjaxTimerBehavior.java:78)
              at
org.apache.wicket.ajax.AbstractAjaxTimerBehavior.renderHead(AbstractAjaxTimerBehavior.java:66)
              at org.apache.wicket.Component.renderHead(Component.java:2182)
              at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer$1.component(HtmlHeaderContainer.java:209)
              at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:820)
              at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:835)
              at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:835)
              at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:835)
              at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:860)
              at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer.renderHeaderSections(HtmlHeaderContainer.java:200)
              at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer.onComponentTagBody(HtmlHeaderContainer.java:134)
              at
org.apache.wicket.Component.renderComponent(Component.java:2104)
              at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1294)
              at org.apache.wicket.Component.render(Component.java:1931)
              at org.apache.wicket.Component.render(Component.java:1894)
              at
org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:223)
              at
org.apache.wicket.markup.resolver.HtmlHeaderResolver.resolve(HtmlHeaderResolver.java:81)
              at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1206)

Unfortunately, I'm a bit too busy at this time to figure out what
exactly the problem is, but I left the issue open. It seems hard to
fix without having a construct like our 2.0 adventure had.

We have been down this road too many times and we keep forgetting them
(or ignoring until we can't bare them)  I'd hate to not fix this one
once and for all.

Me too. Maybe Juergen/ someone else has a good idea?

Eelco

Reply via email to