Am 25.06.2010 20:09, schrieb Jeremy Thomerson:
If you want to do this, you are basically using the single-page paradigm
where your content is always a panel. Basically you just create a single
page, and then all of your content goes into panels instead of pages with
markup inheritance. Then
Hello all,
I would like to extend the Markup Inheritance example
(http://wicket.apache.org/examplemarkupinheritance.html) by replacing
the content part of the page (i.e. the wicket:child) using Ajax.
I tried to replace the BookmarkablePageLink on the BasePage with an
AjaxLink but this does not
What you are trying to accomplish doesn't require markup inheritance.
You can use a panel and replace it with an Ajax link.
That panel could be nested within wicket children participating in
markup inheritance, but that's another matter. The panel should be
the component added to the
If you want to do this, you are basically using the single-page paradigm
where your content is always a panel. Basically you just create a single
page, and then all of your content goes into panels instead of pages with
markup inheritance. Then swap the panel in your link and add it to the ajax
