In my humble opinion: The most important thing that you should know are models en how powerfull they can be used. Models can be quite confusing, especially to programmers who've just started using Wicket. I remember how I struggled with the concept, when I started to use Wicket.
How and when to detach them, how to use them when using an ORM-framework, etc. Ted 2011/7/28 Carl-Eric Menzel <cmen...@wicketbuch.de> > On Thu, 28 Jul 2011 11:10:30 +0300 > Martin Makundi <martin.maku...@koodaripalvelut.com> wrote: > > > > * "compressing" code by use of ids matching property names combined > > > with CompoundPropertyModel and/or PropertyListView > > > > Oh.. that will lead to fragility. > > It can, but in my experience it hasn't. Our domain objects rarely > change, and if they do, our unit tests catch that immediately. The page > doesn't even render if the property model doesn't work, so if you have > a simple "tester.startPage(MyPage.class);" you're safe enough in most > cases. > > This is actually a good point to make for the list: > > - Unit test everything you can using WicketTester. It doesn't do > everything, but it's invaluable as a smoke test at the very least. If > possible, try and check stuff like visibility and enabled state of > your components too. > > Carl-Eric > www.wicketbuch.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
