MockWebApplication calls twice the detach method of cycle.
I opened a issue and sent a patch:
https://issues.apache.org/jira/browse/WICKET-3994
The solution seems very trivial to me so I ask if it may be verified and
eventually scheduled for Wicket 1.4.19.
Thanks
Daniele
It happens when the maximum amount of heap memory is reached.
The solution is to increase a dedicated virtual machine parameter to a higher
value.
For example if you wish to increase to 256 megabytes use this:
-XX:MaxPermSize=256m
in your eclipse.ini file or in the right file of your
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
daniele.cremon...@ext.efsa.europa.eu wrote:
Hi everybody,
My problem is I have to test a Page that should prevent lost
that the
database ORM provider's locking works property, or at least I would.
To make sure nobody turns off the optimistic locking in the future,
just add in a unit test case that validates that the optimistic
locking is turned on by checking the metadata.
On Mon, Oct 11, 2010 at 4:00 AM, 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
