RE: Testing concurrant updates on database

2010-10-11 Thread CREMONINI Daniele
...@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

Re: Testing concurrant updates on database

2010-10-11 Thread James Carman
] 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

RE: Testing concurrant updates on database

2010-10-11 Thread CREMONINI Daniele
] 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

Testing concurrant updates on database

2010-10-08 Thread CREMONINI Daniele
Hi everybody, My problem is I have to test a Page that should prevent lost updates via optimistic lock checking. I resolved the problem using JPA optimistic lock and if I use two different browsers then the Page works in the desired way. The problem comes in the test phase: to emulate two

Re: Testing concurrant updates on database

2010-10-08 Thread James Carman
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