The subject of re-invoking Application#init() came up a couple of years ago in a related discussion. http://mail-archives.apache.org/mod_mbox/wicket-dev/201109.mbox/%3c4e721208.5030...@apache.org%3E
Since the current design is not idempotent I think it would need some wicket-core refactoring to work nicely. On Thu, Aug 1, 2013 at 10:02 AM, Decebal Suiu <decebal.s...@asf.ro> wrote: > Hi > > I'm the creator of wicket-plugin [1] and pf4j [2] and I'm very sensible at > (wicket) hot swap. > Play is stateless. So, it can unload the Controller, forget all the fields > and load and initialize it again. > True (generic) hot swap it hard to achieve but I will try to do incremental > steps to see what I can do with my custom class loader (PluginClassLoader) > with minimal memory leaks and minimal application restart:) > It's interesting if I can use the same plugin (module) framework for the > entire stack (web layer, service layer, persistence layer). > My question is: I can monitor my wicket plugins to see modifications on > class files, I can dispose my plugin class loader, I can create a new > plugin > class loader but can I init again my WicketApplication (programmatically)? > It should be easy more for a stateless web application (framework). > Make sense my idea with reinit wicket application? I see many problems with > this approach and I don't know if it's possible but it's easy to put some > questions :) > > PS I don't want to discuss in this post about OSGI > > [1] https://github.com/decebals/wicket-plugin > [2] https://github.com/decebals/pf4j > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-hot-reloading-Proof-of-concept-tp4660575p4660627.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
