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]
