On Jul 17, 2005, at 1:18 PM, Johan Compagner wrote:


I'm also trying to find out how I can let dynamically reloading code work better. It would be awesome to start Wicket like this and then be able to just change code and introduce new pages (and other code) without having to restart the servlet engine ever again.



Does't support IDEA hotcode replacement? Or whatever name there is for that kind of behaviour? Just start the proces in debug mode. Debug. Change a class. Save/ Compile and the Debugging JVM does the replace of the class completely live (can't do it for everything for example additions to the class like variables or methods (that last thing i still don't get but i guess it has something to do with the serialversionuid that is generated from methods and vars) Because a added method shouldn't effect the in mem state of an instanceof of that class..

Yeah that is one of the problems. I was thinking of making Wicket more aware of this and simply reloading itself if something changes that is incompatible. Like objects in the session or the structure of a page class that is already referenced.

I don't mind losing the state (because of reloading) for more complex changes.

 S.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to