eld for the entities version
> 2) implementation of FlushEntityEventListener with onFlushDirty() method
> containing a check on the version which throws a StaleObjectStateException
> when needed
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.c
implementation of FlushEntityEventListener with onFlushDirty() method
containing a check on the version which throws a StaleObjectStateException
when needed
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718501.html
Sent fro
s, it seems like Hibernate ignores the
value that is set to version. My Hibernate knowledge isn't that great, so
maybe I'm not making any sense :)
So yeah, I'm still not sure what I'm supposed to do.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tape
:)
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718431.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---
Thanks for the ideas, I will look into this :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718431.html
Sent from the Tapestry - User mailing list archive at Nabble.com
don't do update and show some error
}
}
Really don't know what's best practice to implement something like this.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718430.html
Sent from the Tapestry - User
e of it.
> So you mean I have to use Persist instead of activation context?
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718420.html
> Sent from
Index.tml:
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718425.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-m
On Fri, 30 Nov 2012 10:08:54 -0200, nquirynen
wrote:
Hi,
Hi!
Thanks for the explanation. Yes with "I understand its not working" I
meant my approach is failing. I understand optimistic locking is
working, but just don't know how to make use of it.
So you mean I have to use Persist ins
st
> don't know how to make use of it.
> So you mean I have to use Persist instead of activation context?
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718420.html
> Sent
sage in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718420.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry
Should have been
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718416.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To
setters
}
Then you can submit the version as a hidden element on your form and
hibernate will throw an exception if the versions don't match.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413p5718415.html
Sent
On Fri, 30 Nov 2012 08:47:55 -0200, nquirynen
wrote:
Hi,
Hi!
When I submit the form it will always first get the Person object again
through onActivate so I understand why this isnt working.
It's actually working. Optimistic locking doesn't seem to actually be what
you think it is. Hi
message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-optimistic-locking-tp5718413.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.
15 matches
Mail list logo
