Re: Settting of PageManagerProvider is overridden in debug mode
On Tue, Oct 11, 2011 at 12:58 AM, Chris Colman
chr...@stepaheadsoftware.com wrote:
I have a workaround that's probably a bit of a hack but it works ;)
Yep, we are aware that IInitializers override Application's
configuration: https://issues.apache.org/jira/browse/WICKET-4088
I just removed the autoregistering of DebugDiskDataStore when
wicket-devutils is enabled:
https://issues.apache.org/jira/browse/WICKET-4120.
Now if someone wants to browse the disk store she will have to
register it manually in her Application#init().
I overwrite Application#validateInit() and set it there:
protected void validateInit()
{
super.validateInit();
setPageManagerProvider(new MyPageManagerProvider());
}
From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
Sent: Tuesday, 11 October 2011 8:24 AM
To: users@wicket.apache.org
Subject: Settting of PageManagerProvider is overridden in debug mode
In debug mode, setting the page manager provider like this:
setPageManagerProvider(new MyPageManagerProvider(this));
in MyApplication#init()
gets overridden because after the derived class init() is called
Application executes some debug behaviour if in debug mode. This
behaviour always sets the PageManagerProvider to the
DebugPageManagerProvider, overriding any setting made in the derived
class' init() method. I need a custom PageManagerProvider in both debug
and production modes.
Is there any way around this?
Yours sincerely,
Chris Colman
Pagebloom Team Leader,
Step Ahead Software
pagebloom - your business your website growing together
Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120
Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au
Website:
http://www.pagebloom.com blocked::http://www.pagebloom.com/
http://develop.stepaheadsoftware.com
blocked::http://develop.stepaheadsoftware.com/
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Settting of PageManagerProvider is overridden in debug mode
In debug mode, setting the page manager provider like this: setPageManagerProvider(new MyPageManagerProvider(this)); in MyApplication#init() gets overridden because after the derived class init() is called Application executes some debug behaviour if in debug mode. This behaviour always sets the PageManagerProvider to the DebugPageManagerProvider, overriding any setting made in the derived class' init() method. I need a custom PageManagerProvider in both debug and production modes. Is there any way around this? Yours sincerely, Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au Website: http://www.pagebloom.com blocked::http://www.pagebloom.com/ http://develop.stepaheadsoftware.com blocked::http://develop.stepaheadsoftware.com/
RE: Settting of PageManagerProvider is overridden in debug mode
I have a workaround that's probably a bit of a hack but it works ;)
I overwrite Application#validateInit() and set it there:
protected void validateInit()
{
super.validateInit();
setPageManagerProvider(new MyPageManagerProvider());
}
From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
Sent: Tuesday, 11 October 2011 8:24 AM
To: users@wicket.apache.org
Subject: Settting of PageManagerProvider is overridden in debug mode
In debug mode, setting the page manager provider like this:
setPageManagerProvider(new MyPageManagerProvider(this));
in MyApplication#init()
gets overridden because after the derived class init() is called
Application executes some debug behaviour if in debug mode. This
behaviour always sets the PageManagerProvider to the
DebugPageManagerProvider, overriding any setting made in the derived
class' init() method. I need a custom PageManagerProvider in both debug
and production modes.
Is there any way around this?
Yours sincerely,
Chris Colman
Pagebloom Team Leader,
Step Ahead Software
pagebloom - your business your website growing together
Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120
Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au
Website:
http://www.pagebloom.com blocked::http://www.pagebloom.com/
http://develop.stepaheadsoftware.com
blocked::http://develop.stepaheadsoftware.com/
Start.java in debug mode jetty hangs up
Hi I try to start jetty via in debug mode
Here is Start.java
Server server = new Server();
SocketConnector connector = new SocketConnector();
// Set some timeout options to make debugging easier.
connector.setMaxIdleTime(1000 * 60 * 60);
.
try {
System.out.println( STARTING EMBEDDED JETTY SERVER, PRESS
ANY KEY TO STOP);
server.start();
System.in.read();
System.out.println( STOPPING EMBEDDED JETTY SERVER);
// while (System.in.available() == 0) {
// Thread.sleep(5000);
// }
server.stop();
server.join();
} catch (Exception e) {
.
}
I took above code from wicket.apache.org -- quickstart
My problem is when I try to launch Start.java in debug mode, jetty seems
starts (it hangs actually) and when i try to reach http://localhost:8080 it
gives :
HTTP ERROR: 503
Problem accessing / Reason:
SERVICE_UNAVAILABLE
Any suggestions.
(There are no error logs )
Thanks.
Re: debug mode
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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: debug mode
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 Papegaaijemond.papega...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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
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 Ipsonjohn_ip...@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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
