Re: Hot deployment / code swapping

2008-12-12 Thread samk
See Thread at: http://www.techienuggets.com/Detail?tx=51475 Posted on behalf of a User I also have the same problem. Even I added getResourceSettings().setResourcePollFrequency(Duration.ONE_SECOND); to WebApplication class. I am using wicket 1.3.4. Before Wicket come to Apache I never have

Re: Hot deployment / code swapping

2008-12-12 Thread Igor Vaynberg
wicket has never redeployed changes made to class files. this is accomplished by the jvm when the app is ran in debug mode. changes to .html and other resources such as .css are reflected if the application is launched in development mode. -igor On Thu, Dec 11, 2008 at 11:03 PM, s...@twinix.com

Re: Hot deployment / code swapping

2008-09-11 Thread pixologe
Martijn Dashorst wrote: Wicket can't magically detect changes that are not on the classpath. Well, you never what what Frameworks might be able to do below the hood. And with all the magical things wicket can do, I wouldn't have been too surprised to find a config param pointing to my

Re: Hot deployment / code swapping

2008-09-10 Thread Piller Sébastien
Hi, if your app is configured to run in developpment mode, hot deployment should work as expected (at least for html templates). afaik, it doesn't apply for changes in classes files. You have to redeploy to get the changes in class files. pixologe a écrit : Hi everybody, I have read in

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Thanks for your reply. The app is running in development mode and I did not change anything in the quickstart project, however there's no re-deployment at all. :-/ Other wicket users out there, does this work for you? If yes: HTML only or classes too? Just wondering what exactly is the way it

Re: Hot deployment / code swapping

2008-09-10 Thread Witold Czaplewski
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, in Application take a look at getResourceSettings().setResourcePollFrequency(Duration.ONE_SECOND); which should at least work for resource files (like html-templates or property-files). Witold Am Wed, 10 Sep 2008 03:57:22 -0700 (PDT) schrieb

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
The maven jetty plugin needs to be configured separately. See its documentation regarding hot deployment. Martijn On Wed, Sep 10, 2008 at 1:44 PM, pixologe [EMAIL PROTECTED] wrote: Thanks for your reply. The app is running in development mode and I did not change anything in the quickstart

Re: Hot deployment / code swapping

2008-09-10 Thread Florian Sperber
Hi, I use eclipse as a development environment and eclipse supports in the debug mode a fairly good hotreplace of changed java-code (not always but often enough :-)). Kind regards Florian Sperber pixologe schrieb: Thanks for your reply. The app is running in development mode and I did not

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Thanks - I saw this one before, it is set to 1 second by default... but has no effect for me ... Witold Czaplewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, in Application take a look at getResourceSettings().setResourcePollFrequency(Duration.ONE_SECOND); which

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Yeah I know - but there are several reasons why I do not like working with it. Hot swapping is not enough to make me change ;-) Netbeans is capable of replacing java code, too - you just have to tell it when to do this... :) Florian Sperber wrote: Hi, I use eclipse as a development

Re: Hot deployment / code swapping

2008-09-10 Thread Uwe Schäfer
pixologe schrieb: Thanks - I saw this one before, it is set to 1 second by default... but has no effect for me ... did anyone mention javarebel? http://zeroturnaround.com this one aims to solve this exact problem. i use it, and i´m quite happy with it. cu uwe

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
No, there isn't even an init method in the untouched quickstart project :) According to Martijn's message, there has some jetty config to be done... Currently having a look Thanks so far... Witold Czaplewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it works for me.

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Hi Martijn, So this means that the wicket quickstart project does NOT do it out of the box? Which obviously goes for non-maven-projects too then? That's good to know, I obviously have been terribly misinformed then... Even though it will obviously take me some more time to figure out how this

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
In this thread, no. However, free software (and - if possible - genuine solutions) is preferred of course. I might consider using JavaRebel (since there is obviously no out-of-the-box-support as have thought), however some time would have to be spent first with evaluation etc... In my present

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
The maven jetty plugin is not meant for development, but for quick demos. Stop trying to use the jetty plugin for something it is not intended for. The Wicket quickstart project provides a very well functioning embedded jetty server, which runs like a charm in the Eclipse debugger (and IDEA and

Re: Hot deployment / code swapping

2008-09-10 Thread Eyal Golan
Regarding the embedded jetty, do you know if it is possible to point it to an external WAR so it will be as if deployed as well? I looked into Jetty's document but didn't find. On Wed, Sep 10, 2008 at 4:17 PM, Martijn Dashorst [EMAIL PROTECTED] wrote: The maven jetty plugin is not meant for

Re: Hot deployment / code swapping

2008-09-10 Thread Roman Zechner
I am using the maven jetty plugin in development and it works fine for me. I don't see why you shouldn't use it as Martijn pointed out? If there's a need, I can post the required configuration here. I am working under WinXP, all my stuff is redeployed after changes have been made when working

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Martijn Dashorst wrote: The maven jetty plugin is not meant for development, but for quick demos. Well, at least to me, this was not obvious. Good to know. However, also after starting the quickstart project within the IDE, there is not hot deployment of classes or HTML files. Same

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
Because of discussions such as this. I'd like folks to actually use an IDE and the quickstart as it was intended. We made the quickstart so that this type of questions don't get asked—saves time, energy and frustrations on both ends. mvn jetty:run is nice to quickly test a web project, but not

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
Then you don't have netbeans configured to copy the html over to the classpath, like I told in my first reply. Martijn On Wed, Sep 10, 2008 at 3:56 PM, pixologe [EMAIL PROTECTED] wrote: Martijn Dashorst wrote: The maven jetty plugin is not meant for development, but for quick demos. Well,

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Well, that was sort of the initial question... Does wicket itself or the quickstart project provide any more hot deployment than my IDE's? (Which is, in case of netbeans, replacing classes in debug mode)... Still, I am not sure what the answer is... Martijn Dashorst wrote: Because of

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
You mean the one in which you say one shouldn't use mvn jetty plugin for development? Hmmm... it says The Wicket quickstart project provides a very well functioning embedded jetty server, which runs like a charm in the Eclipse debugger (and IDEA and Netbeans debugger) providing everything

Re: Hot deployment / code swapping

2008-09-10 Thread Roman Zechner
I don't know about the time efforts in using your suggested way, but by using the maven jetty plugin you only have to configure the project once, so each new developer joining the project doesn't have to make any configuration on its's IDE. In that way you always provide kind of a quickstart

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
Hmm sorry, I had it typed in but apparently didn't send it. You have to tell Maven, Jetty, Your IDE that it needs to copy the html files from the src directory to the classpath. Wicket Quickstart does this on each compile because of the resources section. Apparently the jetty plugin doesn't pick

Re: Hot deployment / code swapping

2008-09-10 Thread Martijn Dashorst
I don't have to configure anything. run the archetype command, import project into eclipse, right click on Start class select Debug as Java application and I'm done. I don't know what configuration you are talking about, but I don't have to meddle with external jetty configurations, making sure

Re: Hot deployment / code swapping

2008-09-10 Thread Igor Vaynberg
wicket does not provide anything in the way of deployment. what it does in dev mode is monitor any changes to html/properties files and when they are changed it evicts them from cache so next time you reload the page you see the changes. obviously wicket does not know where your source file live,

Re: Hot deployment / code swapping

2008-09-10 Thread Roman Zechner
Sorry, I misinterpreted your previous post. I will check the bonus chapters of WiA. Roman Martijn Dashorst wrote: I don't have to configure anything. run the archetype command, import project into eclipse, right click on Start class select Debug as Java application and I'm done. I don't know

Re: Hot deployment / code swapping

2008-09-10 Thread pixologe
Cool... thanks a lot. I will check this out tomorrow! Thanks for sharing this piece have a nice evening. Roman Zechner | Liland wrote: don't worry, we had our own problems in the beginning to get this stuff working. here we go - hope I haven't forgotten anything. you need to modify

Re: Hot deployment / code swapping

2008-09-10 Thread Roman Zechner
Now I am using the embedded jetty server as suggested in the bonus chapters of Wicket in Action. But Spring complains that it is missing a bean dataSource, so I set the jetty deployment descriptor with WebAppContext bb = new WebAppContext();