...@carmanconsulting.com [mailto:jcar...@carmanconsulting.com] On
Behalf Of James Carman
Sent: 08 October 2010 12:13
To: users@wicket.apache.org
Subject: Re: Testing concurrant updates on database
What exactly are you trying to test? Are you trying to test the
optimistic locking? You didn't write
] On
Behalf Of James Carman
Sent: 08 October 2010 12:13
To: users@wicket.apache.org
Subject: Re: Testing concurrant updates on database
What exactly are you trying to test? Are you trying to test the
optimistic locking? You didn't write that. If you want to test that
you actually have
] On
Behalf Of James Carman
Sent: 11 October 2010 10:09
To: users@wicket.apache.org
Subject: Re: Testing concurrant updates on database
You're really not supposed to be monkeying with the version property
yourself. You're supposed to let the ORM provider do that. What I
would do is create a hidden field
What exactly are you trying to test? Are you trying to test the
optimistic locking? You didn't write that. If you want to test that
you actually have optimistic locking turned on, then you can do that
by checking the metadata.
On Fri, Oct 8, 2010 at 3:27 AM, CREMONINI Daniele
