Why you littleOn 9/8/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
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 d
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
On 9/8/06, Chan Man Kam <[EMAIL PROTECTED]> wrote:
Are there any method to degrade the all the wicket AJAXcomponent to a normal request? It may be useful for debugging.there is no way to "degrade" this off some switch. wicket provides what we call ajax "fallback" components, these components use aj
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
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 in
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 h
