Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Good thought. I considered OSGi, but there's the resource constraint to consider. The OSGi containers I've tried out have significant memory footprints without even having any bundles deployed to them. I'd be happy to be corrected on that point, though. Commented Apr 21, 2012 at 0:02
  • 1
    Another resource to consider is your time. OSGi is extremely invasive into the architecture of your app, and the classloading rules it imposes can take a while to learn. It's fine once you are up and running (and having someone implement update is great!) but don't think this would be a day's work. Commented Jun 14, 2012 at 11:20