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
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
This is of course discussed in the awesome, indispensable, always to
go to, why don't I have this on my book shelve, let's make sure Eelco
and Martijn can have a beer, Wicket in Action, chapter 14.
But since you don't have it, or haven't gotten that far (yet), in
development mode Wicket does
