You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by John Ipson <jo...@yahoo.com> on 2009/07/14 19:15:02 UTC
debug mode
Hello,
Has anyone ever run across extremely slow debug mode in wicket/eclipse integration?
Eclipse 3.4
Wicket 1.4
When choosing "Run as...", the application is very fast.
When choosing "Debug as..." the application is 20 times slower.
I watch each jar get loaded into the application at a very slow rate.
I've run the application in Jetty and JBoss, so I believe it is a wicket thing. I wonder if there is a setting in wicket.
Thanks,
John
Re: debug mode
Posted by Igor Vaynberg <ig...@gmail.com>.
i use wicket and eclipse+debug every day and i have never experienced
something like this. the app runs a little slower in debug mode, most
times unnoticeably so.
-igor
On Tue, Jul 14, 2009 at 10:15 AM, John Ipson<jo...@yahoo.com> wrote:
> Hello,
>
> Has anyone ever run across extremely slow debug mode in wicket/eclipse integration?
>
> Eclipse 3.4
> Wicket 1.4
>
> When choosing "Run as...", the application is very fast.
> When choosing "Debug as..." the application is 20 times slower.
>
> I watch each jar get loaded into the application at a very slow rate.
>
> I've run the application in Jetty and JBoss, so I believe it is a wicket thing. I wonder if there is a setting in wicket.
>
> Thanks,
> John
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: debug mode
Posted by Nicolas Melendez <nm...@getsense.com.ar>.
dont' use vista, desactivate antivirus and stop playing street fighter
IV while you are programming ;)
On Wed, Jul 15, 2009 at 9:14 AM, Emond
Papegaaij<em...@topicus.nl> wrote:
> I've had similar problems when using method breakpoints on inner classes.
> Removing the breakpoint speeds up the entire application dramatically (the
> breakpoint also doesn't work). So try removing your breakpoints.
>
> Emond
>
> On Tuesday 14 July 2009 19:15:02 John Ipson wrote:
>> Has anyone ever run across extremely slow debug mode in wicket/eclipse
>> integration?
>>
>> Eclipse 3.4
>> Wicket 1.4
>>
>> When choosing "Run as...", the application is very fast.
>> When choosing "Debug as..." the application is 20 times slower.
>>
>> I watch each jar get loaded into the application at a very slow rate.
>>
>> I've run the application in Jetty and JBoss, so I believe it is a wicket
>> thing. I wonder if there is a setting in wicket.
>>
>> Thanks,
>> John
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: debug mode
Posted by Emond Papegaaij <em...@topicus.nl>.
I've had similar problems when using method breakpoints on inner classes.
Removing the breakpoint speeds up the entire application dramatically (the
breakpoint also doesn't work). So try removing your breakpoints.
Emond
On Tuesday 14 July 2009 19:15:02 John Ipson wrote:
> Has anyone ever run across extremely slow debug mode in wicket/eclipse
> integration?
>
> Eclipse 3.4
> Wicket 1.4
>
> When choosing "Run as...", the application is very fast.
> When choosing "Debug as..." the application is 20 times slower.
>
> I watch each jar get loaded into the application at a very slow rate.
>
> I've run the application in Jetty and JBoss, so I believe it is a wicket
> thing. I wonder if there is a setting in wicket.
>
> Thanks,
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org