Well I would recommend adding this in your Application class:
@Override
protected void init() {
...
if(isDevelopmentMode()) {
...
IRequestCycleSettings#**setTimeout();
...
}
...
}
public boolean isDevelopmentMode() {
return (getConfigurationType() ==
I don't see a reason why this setting should be modified at all.
It is normal that while debugging it will take more time. This exception is
harmless while you debug another (a real) problem.
I'd change the value of this setting only if I know that there are paths in
the code which need more time
Nice, thanks for that Martin.
We've carried this webapp since early versions of wicket and we haven't yet
upgraded older utility methods.
Goes to shows how nicely some of the API carried forward in Wicket :)
~ Thank you,
Paul Bors
On Mon, Jan 28, 2013 at 10:57 AM, Martin Grigorov
Sure things men. But I need to raise this timeout in dev mode since I want
to have the graphical result of my (Ajax) request after having browsed
through the code: when the browser throws an error, I have no way to know
if what I have seen in my debugger is correct or not.
Anyway: +1 for
Better find out why it takes that long and try to make the request
processing faster.
On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil goupilpie...@gmail.comwrote:
Thanks a lot, it works!
Cheers,
Pierre
On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier s...@meiers.net wrote:
You can adjust
As I said, it's only when using (Eclipse) debugger. When I go from methods
to breakpoints and back again, only one minute is a bit short.
But with Sven's solution, I have what I need.
Cheers, men!
Pierre
On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov mgrigo...@apache.orgwrote:
Better
Good afternoon,
When debugging through my Wicket code, I often get this exception:
CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute
Is there anything I can do to rise up this timeout, please?
Regards,
Pierre Goupil
--
Parce que c'est la nuit qu'il est beau de
You can adjust IRequestCycleSettings#setTimeout().
Sven
On 01/26/2013 06:03 PM, Pierre Goupil wrote:
Good afternoon,
When debugging through my Wicket code, I often get this exception:
CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute
Is there anything I can do to
Thanks a lot, it works!
Cheers,
Pierre
On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier s...@meiers.net wrote:
You can adjust IRequestCycleSettings#**setTimeout().
Sven
On 01/26/2013 06:03 PM, Pierre Goupil wrote:
Good afternoon,
When debugging through my Wicket code, I often get this
