On Jan 23, 2008 5:03 PM, Sam Hough <[EMAIL PROTECTED]> wrote: > > Thanks Igor, > > >> 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 > Isn't Wicket a bit different in that it has more server state? So I need to > take more care at least in comparison to struts like webapp with very little > if any session state?
not really...things that change often (db driven data) is usually stored in detachable models, so it is reloaded just as often as in a struts 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. > >huh? > Probably me being thick but what about: User clicks link to create new row > in the database and I create a new link on the page to the new object. I > need to be careful that the page state is not altered until _after_ the db > has confirmed the commit? but you wouldnt create a new link until after you have committed the data... and if you do somehow do it before you commit and there is an error you will probably show a user some error page rather then the ui page they were on...because if the commit is after you have constructed your page there isnt even a way for you to add an error message to that page... > After all those years of struts like frameworks and client server it is > tough for an old brain to learn good habits in this very different model :) > The serialisation between client and server is a PITA and performance hole > but is a safety barrier I've got very used to. So in old school the UI > (HTML/JS) always gets a complete success or failure response while in Wicket > I can accidently update the UI before knowing if this request will end in > success or failure. i just dont see how this is true. eg if you have a link then inside onclick() you know if something is successful or not, and if not then why make any ui changes? -igor > > Cheers > > Sam > > -- > View this message in context: > http://www.nabble.com/db-transaction-boundary-tp15042959p15056622.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]
