> I find that reloading the entire app stack (wicket + spring + > hibernate) every time I change a page class is somewhat overkiller. > When coding simple toy examples restricted to just wicket, the > jetty:run maven plugin monitors my target folder and reload the > application in a matter of a second or a fraction of a second. But > with the entire stack in place this number will be above 5 seconds at > least and up to 20 seconds for realistic-sized applications. Have > anyone worked out a classloader that would selectively reload just the > web tier of the application?
See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket is an unmanaged framework, meaning it depends more on the facilities the JDK provides. Some SDK implementations are working on improved support (I think Johan has some experience with IBM JDK: http://www-128.ibm.com/developerworks/java/jdk/eclipse/ ?) and see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4910812 (and vote!). > Btw, I gave a chance to java hot-code-replacement but it's very limited (it > lets you > modify inside methods but do nothing that alters the class > schema/interface, someone out there would say it sucks) See that issue at SUN. :) Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
