I have this example to show my problem:
This kind of architecture is used in a bigger application with about 30-35 panels where about 10 use Ajax to replace itself. The problem is that after the addOrReplace() the parent to the panel get lost which will lead to findParent() returning null. And because of that, the error "Page not found for component..." will be displayed.
Its like a "ping pong" application which means i dont know what to display next - i get this information from a controller in the backend. For that reason i can not create a flow-based wizard like the wizard example because i dont know yet what to display.
As adviced in the mailing list i created this jira issue. I dont know if this is a bug or a feature request.
WICKET-4910 AjaxSelfUpdatingTimerBehavior broken in Wicket 6.3.0