On Jan 23, 2008 6:38 AM, Sam Hough <[EMAIL PROTECTED]> wrote: > > Where is the typical place to put the transaction boundry in a wicket app?
wherever youd like, wicket apps are no different then other webapps in this regard > If I put it right at the front (servlet filter) then my pure UI components > might get bad state as they won't get rolled back with the database state. huh? > If I put it between my UI components and facade to middle tier then my > components can't take advantage of lazy loading... why not? i use spring's @Transactional and it works just fine. you need to configure openentitymanagerinviewfilter or opensessioninviewfilter depending on what persistance framework you use. > Is the safest bet to have a big divide between UI and middle tier (as if in > different threads and VM)s? So UI components pretty much get back value > objects? no, this is most certainly not the way to go. not having lazy-loading or something like it will either completely break encapsulation ( you need to know the entire set of data your page will need, including data that any component on that page will need - so you can load it all in one shot ) or will cause a heavy db load ( every component retrieving data by issuing queries ) -igor > btw Is there a wicket core dev beer fund or favourite charity? I'm asking a > lot of questions but havn't got the time or energy to help out. > > Cheers > > Sam > -- > View this message in context: > http://www.nabble.com/db-transaction-boundry-tp15042959p15042959.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
