<html><head> | |
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | |
<title>Chapter 2. Why Gemini Blueprint?</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="Eclipse Gemini Blueprint Reference Guide"><link rel="up" href="introduction.html" title="Part I. Introduction"><link rel="prev" href="eclipse-migration.html" title="Chapter 1. Spring Dynamic Modules becomes Eclipse Gemini Blueprint"><link rel="next" href="requirements.html" title="Chapter 3. Requirements"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="why-Spring DM"></a>Chapter 2. Why Gemini Blueprint?</h2></div></div></div><p>The Spring Framework is the leading full-stack Java/JEE | |
application framework. It provides a lightweight container and a | |
non-invasive programming model enabled by the use of dependency | |
injection, AOP, and portable service abstractions. The OSGi Service | |
Platform offers a dynamic application execution environment in which | |
modules (bundles) can be installed, updated, or removed on the fly. It | |
also has excellent support for modularity and versioning.</p><p>Gemini Blueprint makes it easy to write Spring applications | |
that can be deployed in an OSGi execution environment, and that can take | |
advantage of the services offered by the OSGi framework. Gemini Blueprint | |
support also makes development of OSGi applications simpler and more | |
productive by building on the ease-of-use and power of the Spring | |
Framework. For enterprise applications, the combination of Eclipse Gemini Blueprint | |
and the OSGi platform provides:</p><div class="itemizedlist"><ul type="disc"><li><p>Better separation of application logic into modules, with | |
runtime enforcement of module boundaries</p></li><li><p>The ability to deploy multiple versions of a module (or | |
library) concurrently</p></li><li><p>The ability to dynamically discover and use services provided | |
by other modules in the system</p></li><li><p>The ability to dynamically install, update and uninstall | |
modules in a running system</p></li><li><p>Use of the Spring Framework to instantiate, configure, | |
assemble, and decorate components within and across modules.</p></li><li><p>A simple and familiar programming model for enterprise | |
developers to exploit the features of the OSGi platform.</p></li></ul></div><p>We believe that the combination of OSGi and Spring offers a | |
comprehensive model for building enterprise applications.</p><p>The OSGi Alliance found valuable the programming model proposed by Gemini Blueprint (then Spring DM) and, | |
in OSGi 4.2, standardized it by introducing the Blueprint Container, as part of the Compendium | |
services.</p></div><div xmlns:fo="http://www.w3.org/1999/XSL/Format" class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="eclipse-migration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="requirements.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. Spring Dynamic Modules becomes Eclipse Gemini Blueprint </td><td width="20%" align="center"><span style="color:white;font-size:90%;"><a href="http://www.SpringSource.com/" title="SpringSource - Spring from the Source">Sponsored by SpringSource | |
</a></span></td><td width="40%" align="right" valign="top"> Chapter 3. Requirements</td></tr></table></div></body></html> |