Survey of frameworks that can be used to support plugability and/or modularity

...

The OSGi HTTP Service is a Servlet Container on which servlets can be deploy dynamically and programmatically. To give an example of how this could benefit DSpace, because te servlet can be deployed dynamically into the container, it doesn't actually have to reside in the webapplication war file or be described in the web deployment descriptor (web.xml) thus in a modular DSpace world, a module could deploy servlets into the main DSpace webapplication context without any need to do a build that combines them all together. simply have your module distributed in an OSGi bundle (a.k.a. a Java Jar with a little extra manfest info) and delopy them into the OSGi Framework and tey come up in the webapplication. – MarkDiggory 10:17, 11 November 2006 (EST)

While OSGi's ability to deploy and undeploy these bundles very dynamically is interesting, its more the method of deployment that is of value to a DSpace Application which will provide a means to keep the DSpace modules very separate from one another at compile time, bringing them together to go on the server only at the time of deployment. So we get two things out of OSGi that are of the greatest benefit to DSpace, (1) a clear deployment pattern and (2) a clear separation of concerns for modules. – MarkDiggory 10:17, 11 November 2006 (EST)

...

Searching for research in the area of integrating Cocoon, Spring and OSGi, please post it here – MarkDiggory 08:53, 13 November 2006 (EST)

...