Ok, ok. What WAS I thinking? :)FrankOn 9/8/06, Johan Compagner [EMAIL PROTECTED] wrote:
Frank frank!this is bad advice!don't call the configure method yourself. That shouldn't be done.
Because configure m ethod is always already calledWhat you should do is set in through the web.xml in deployment
Are there any method to degrade the all the wicket AJAX
component to a normal request? It may be useful for debugging.
I am using jetty http server 5.0, wicket 1.2.2 and jetty launcher
to develop and test my project, but after I changed my java
source code, the server cannot updated until I
What I do to hot deploy in Eclipse is setting configure to DEVELOPMENT in init:...class MyApplication extends WebApplication {... init() {... configure(DEVELOPMENT);... }
...}This gives you hot update of resources (HTML). For java code run the jetty launcher as debug. Debug gives you hot deploy.If
Frank frank!this is bad advice!don't call the configure method yourself. That shouldn't be done.Because configure m ethod is always already calledWhat you should do is set in through the web.xml in deployment mode (or developerment if you always want to be in development mode)
But if you have it
billen-IgorOn 9/8/06, Johan Compagner [EMAIL PROTECTED] wrote:
Frank frank!this is bad advice!don't call the configure method yourself. That shouldn't be done.Because configure m ethod is always already calledWhat you should do is set in through the web.xml in deployment mode (or developerment if
