t; layer and it sounds like a reasonable approach based on my query from
> > fellow
> > colleges on this forum -- Steve
> > --
> > View this message in context:
> > http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24167367.html
> > Sent from the Wicket - User maili
w, I have created a lock table in memory at the app
> layer and it sounds like a reasonable approach based on my query from
> fellow
> colleges on this forum -- Steve
> --
> View this message in context:
> http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24167367.html
> S
layer and it sounds like a reasonable approach based on my query from fellow
colleges on this forum -- Steve
--
View this message in context:
http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24167367.html
Sent from the Wicket - User mailing list archive at
>> > seems like such a normal condition for any application that has multiple
>> > writers, so I thought I would see what is a typical approach within web
>> > apps
>> > -- something I am very new at.
>> > --
>> > View this message in context:
>>
has multiple
> > writers, so I thought I would see what is a typical approach within web
> > apps
> > -- something I am very new at.
> > --
> > View this message in context:
> > http:/
pproach within web
> apps
> -- something I am very new at.
> --
> View this message in context:
> http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24158076.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
so I thought I would see what is a typical approach within web apps
-- something I am very new at.
--
View this message in context:
http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24158076.html
Sent from the Wicket - User mailing list archive at Nabbl
> feedback when someone else is in edit "thinking" mode, I don't think I
> would
> use it.
> --
> View this message in context:
> http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24157353.html
> Sent from the Wicket - User mailing list archive at Nabble.com
ay to give user
feedback when someone else is in edit "thinking" mode, I don't think I would
use it.
--
View this message in context:
http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24157353.html
Sent from the Wicket - User mailing l
Why not just lock the relevant row of the relevant table? Versioning
is for optimistic locking, but it sounds to me like you want plain old
pessimistic locking.
In Hibernate, check out LockMode.UPGRADE.
Scott
On Mon, Jun 22, 2009 at 3:58 PM, Steve Tarlton wrote:
> I thought I would throw this
I thought I would throw this one out to the user group and see if it makes
sense or am I over complicating things. I am implementing a check list
system using Wicket-Hibernate-Spring. There could potentially be more than
one person trying to edit a given check item within the list and I want to
be
11 matches
Mail list logo
