Hi all, 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? Is there any plan for this or a related solution? I know tapestry 5 has its own fix-and-see class loading scheme. I worked a bit with zk which gets the same effect by means of scripting. I like the wicket way a lot more than zk's or tapestry's and I think hot-reloading can be a killer feature. 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) and it doesn't play well with the java-centric approach of wicket, which requires more refactoring and sophisticated coding than others.
Cheers, Carlos ------------------------------------------------------------------------- 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
