Replacement of a markup container with nested components by a panel / fragment

[pasto]

Hi,

I guess, this is the same question as the 'WICKET-1190' issue.

Extending AjaxLazyLoadPanel and overriding the xhtml markup file and the
getLoadingComponent method causes, as soon as there is a child component in
the 'content' component, "Close tag not found for tag" exception.

<wicket:panel xmlns:wicket =
"http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd";>
        <wicket:container wicket:id="content">
                <center> /static/img/small-ajax-loader.gif </center>
        </wicket:container>
</wicket:panel>

The reason is a check in the
'AbstractMarkupSourcingStrategy.onComponentTagBody' method:

if (markupStream.getPreviousTag().isOpen())
{
        markupStream.skipRawMarkup();
        if (markupStream.get().closes(openTag) == false)
        {
                throw new MarkupException(markupStream, "Close tag not found 
for tag: " +
                        openTag.toString() + ". Component: " + 
component.toString());
        }
}

Changing it to:

if (markupStream.getPreviousTag().isOpen())
{
        markupStream.skipToMatchingCloseTag(markupStream.getPreviousTag());
}

seems to work fine.

Is there a reason to not allow replacement of a markup container with nested
components by a panel / fragment? I think, that the definition of
alternative panels (e.g. lazy load panels) would be easier.

Just being curious...

Peter.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Replacement-of-a-markup-container-with-nested-components-by-a-panel-fragment-tp3609276p3609276.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org