On Mon, Mar 30, 2009 at 12:44 PM, Rickard Öberg <[email protected]> wrote:
> We are mainly talking about reloading implementation, right? Since the > bindings would require restart of app? Well, when OSGi detects that classes are needed to be tossed away, it will stop the bundles affected, which in turn are to stop the Qi4j application. However, it is not done that way in Qi4j at the moment as far as I know. I should look into the mechanics of unload a bit more in detail, since it should have changed since the last bootstrap improvements. > As already outlined in a previous post though, it's entirely possible to > have one module create another app as "plugins", which can be restarted > without restarting the encapsulating application. Maybe this would be the > pattern to use here. Uhhh.... Are you sure? If you don't have classloader separation, then there are a lot of problems lurking around the corner with such simplistic approach. Will review later. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
