my hunch would be with the correct use of dwr callback functions
Nathaniel Rahav wrote: > > Greetings, > > I'm working on an Appfuse 1.8.2 SpringMVC app and having a very strange > problem. I dont use a lot of DWR in my app, just a little bit on this one > page where I dont want the user to leave the page. > > Im getting a situation in which the user's action on the page causes a DWR > object on the server to retrieve an object, modify it, and save it to the > database. Then the client side page refreshes itself. > After the page refreshes, sometimes the object shows its new state, and > sometimes it appears the same. > > If I wait a little while, and manually refresh the page, the object then > appears modified. So it appears that my action to the database is taking a > little while to commit. > Is there a way, inside my DWR server side code, to force Spring & > Hibernate > to commit my action immediately, before DWR finishes and returns control > to > the client ? > > thanks in advance, > > Nat > > -- View this message in context: http://www.nabble.com/Database-immediate-commit-with-DWR---tf4552257s2369.html#a12995392 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
