Thanks, I'll try it.
On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <[email protected]>wrote: > Hello, Sebastian. > > You can try to use JRebel (http://zeroturnaround.com/software/jrebel/). > This is a JVM agent, that eliminates the need for redeployment. You can > read about JRebel and Wicket here: > http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/ > > P.S. JRebel is free for opensource projects. > > 2012/9/9 [email protected] <[email protected]> > > > Hi, > > > > we have set up Wicket in OpenMeetings and it is working fine! > > > > However the development cycle is pretty long: > > Every change requires us to recompile and restart the servlet container. > > As we use Wicket + Spring + openJPA a restart takes around 20 seconds > > + compilations time, it takes around 30 seconds in total. > > When working with UI components you regularly sit on your desk and > > wait for this cycle to complete ;) > > > > Is there a way to develop and test Wicket more agile? > > Is there some "Hot-plug" mechanism that does not require to reload the > > whole servlet container with every change? > > > > Thanks! > > Sebastian > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > [email protected] > > > > > > -- > Best Regards, > *Dmitry Zamula* > > Saint-Petersburg, Russia > UTC/GMT +4 hours > > Mobile phone: +7 (904) 646-9254 > Skype Id: brantner_ru > E-mail: [email protected] > -- WBR Maxim aka solomax
