On 5/16/11 10:31 AM, "Scott Wilson" <[email protected]> wrote:
> >> >> * if feasible modules could be packaged/bundled as a self contained >>single archive (zip or jar) supporting a simple "drop in" (manually >>before startup) or through a runtime deployment service. This is the >>area where OSGi might actually be interesting to consider, although I'm >>not convinced (yet) if the technical and infrastructural overhead is >>worth it, yet. A simple "deploy" folder with a file/folder change >>listener might be good enough and is easy enough to write. > >Its a tricky question. I'm similarly in two minds about OSGI. > >Both Shindig and Wookie use XML-based feature loading systems, however >these only inject client-side scripting into widgets/gadgets. Server-side >extensions are harder to manage, which is where OSGI starts to look >attractive. IMHO, OSGI would vastly overcomplicate the solution. I think we can all agree the features that we are looking for are tied to the dynamic modules. OSGI in my experience, ends up polluting the code base and creates a much more complex system than I would want to see. We can override pretty much everything in the Spring application context by adding beans that are marked primary to the scanned classpath...
