The problem is that this leads to a Page not found error. The problem is
that the Panel which should be replaced is still looked up in the
findPage() method. But findPage() returns null on that component, so
this error is thrown.
Am 24.11.2012 21:48, schrieb Sven Meier:
What is the problem?
Sven
On 11/24/2012 08:22 PM, Oliver Zemann wrote:
Hi,
i created a small wicket application to show my problem:
https://github.com/olze/WicketPanelReplace
The first panel gets displayed, after a few seconds it should be
replaced by the second panel. Is there any way to achieve this
behavior with that kind of architecture?
If not, how should a ajax based panel wizard work? Any recommendations?
Thanks in advance.
Oli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
