Where is the typical place to put the transaction boundry in a wicket app?
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. If I put it between my UI components and facade to middle tier then my components can't take advantage of lazy loading... 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? 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]
