The differences are implemented in Application.configure(), so check there for how deployment and development mode differ. I am not aware of any differences in how Wicket handles the component hierarchy. The hierarchy in your java-implementation either is or is not consistent with the hierarchy in your template files. Wicket doesn't do anything to fix or ignore hierarchy issues.
On Tue, 24 May 2011 10:51 -0400, "Brown, Berlin [GCG-PFS]" <berlin.br...@primerica.com> wrote: > I noticed with the web.xml configuration, development mode that I see > more hierarchy exceptions thrown by wicket. Basically, it seems that > wicket ignores some hierarchy or markup issues in development mode and > not in deployment mode. What are the main differences between those > modes and how do I know what exceptions will be thrown? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
