Why? There's nothing keeping you from storing the version too, and checking that against the newly loaded entity... The question is... what do you do when the version is modified from your original object?
Martijn On Mon, Dec 8, 2008 at 9:11 PM, James Carman <[EMAIL PROTECTED]> wrote: > There are many ways to skin a cat. LDMs pretty much throw optimistic > locking out the window, agreed (since they just go get a "fresh" copy of the > object each time typically)? So, if you want to use optimistic locking, > then you shouldn't be using LDMs in the first place. > > On Mon, Dec 8, 2008 at 2:28 PM, Erik van Oosten <[EMAIL PROTECTED]>wrote: > >> So I guess you're not levering the optimistic locking of Hibernate. >> >> Regards, >> Erik. >> >> >> James Carman wrote: >> >>> It would work the same way, since it grabs its stuff up-front. Behind the >>> scenes, you use a LDM as the actual model. >>> >>> On Mon, Dec 8, 2008 at 1:56 PM, Daan van Etten <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>>> Hi James, >>>> >>>> How does this work with a Hibernate-managed object? Did you test it with >>>> Hibernate? >>>> >>>> >>>> >>> >>> >> >> -- >> Erik van Oosten >> http://www.day-to-day-stuff.blogspot.com/ >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
