Jeremy, I just threw together the following, which indicates that at least to me Models are worth 3 of your 10 items.
1. Most components have a backing object of some sort. This object is referenced via a Model. Significantly, the type of the component and the model match (e.g. Label<Integer> has an IModel<Integer>). 2. These objects live in the session and are managed in the session by wicket, so that when the component goes out of scope the object is removed from the session by wicket. 3. Because domain objects are often too large to store in the session there is a LoadableDetachableModel that is responsible for loading the object whenever it is needed in a request and then flushing it at the end of the request via detach(). Cheers, Scott On Wed, Jul 27, 2011 at 3:29 PM, Jeremy Thomerson <jer...@wickettraining.com> wrote: > Hello all, > > I'm writing an article for a Java magazine and would like to include in it > a list of "ten things every Wicket programmer must know". Of course, I have > my list, but I'd be very curious to see what you think should be on that > list from your own experience. Or, put another way, maybe the question > would be "what I wished I knew when I started Wicket" - what tripped you up > or what made you kick yourself later? > > Please reply back if you have input. Please note that by replying, you > are granting me full permission to use your response as part of my article > without any attribution or payment. If you disagree with those terms, > please respond anyway but in your response mention your own terms. > > Best regards, > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
