But that really depends on how you structure your models. If you use models that do the loading once on attach, cache the results, and then unload on detach, you wouldn't have the double loading if you share the model. Instead of passing ids around, you pass around the model of course. Besides that, within one transaction Hibernate caches objects too.
Eelco On 7/16/06, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote: > Another case I just remembered where performance in #1 will be poor is > where you have a page containing a lot of panels, each of them needing > the model object or one of its associations. In #1 the object will be > loaded per panel, but in #2 or #3 you wont have any extra calls. > > Iman > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
