O'Reilly logo
  • William Yeh thinks this is interesting:

Unlike JRebel, the OSGi update process doesn’t depend on a special JVM agent. It also doesn’t have any significant effect on performance. These reasons together mean you can use the OSGi update process in a production environment. The downside is that you have to update and restart the entire bundle, potentially destroying the current state, rather than redefine a single class. If you wanted to keep any previously drawn shapes, you would need to persist them somehow when stopping and restore them when restarting.

From

Cover of OSGi in Action: Creating Modular Applications in Java

Note

HotSwap pros and cons in OSGi.