THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Another solution might be to subclass MarkupContainer.add()
like discussed in WICKET-3045].
The main reason why we removed MarkupContainer.isTransparentResolver()
has been the magic necessary in Wicket's core and the number of issues/questions, where we identified isTransparentResolver()
as the root cause. It all boils down to that with isTransparentResolver()
the markup and component hierarchies get out of sync.
...