> I must admit that I don't get the whole detachable stuff in Wicket. I'm used > to think in horizontal tiers > where one tier does all the caching "automagically" (e.g. 2nd level cache in > JPA/Hibernate) and the > other tiers don't know about that fact.
What models in Wicket can achieve is that data is compressed between requests. This is important because Wicket stores component trees in memory/ on your disk between requests. Obviously the smaller the better there. Detaching is also important when you work with objects as your models that might hold on to resources (e.g. session in Hibernate); detaching lets those objects frees up those resources after a request. Eelco
