Anyone know why Page.detachModels() no longer detaches the models of all child components in 1.3beta3? There is a bunch of code commented out in Page.detachModels() that previously did this. Now it just calls super.detachModels() (on Component) which apparently just detaches the model immediately attached to the Page (which renders the need for Page.detachModels() moot). I searched the lists and the closest thing I found was a reference to https://issues.apache.org/jira/browse/WICKET-418, but that seems to have to do with Ajax requests.
This has broken a JUnit test that was testing a detachable model using WicketTester. The same test passes in Wicket 1.2.6. Is there something different I should be doing in 1.3? -Dan
