Spring Dynamic Modules for OSGi(tm) Service Platforms

Introduction

The Spring Dynamic Modules for OSGi(tm) Service Platforms project makes it easy to build Spring applications that run in an OSGi framework. A Spring application written in this way provides better separation of modules, the ability to dynamically add, remove, and update modules in a running system, the ability to deploy multiple versions of a module simultaneously (and have clients automatically bind to the appropriate one), and a dynamic service model.

OSGi is a registered trademark of the OSGi Alliance. Project name is used pending approval from the OSGi Alliance.

Downloads 

GA release - 1.0.2

• Download
• Reference Documentation
• FAQ
• Known Issues
• Javadocs
• Changelog
  

Latest release - 1.1.0 M2

• Download
• Reference Documentation
• FAQ
• Known Issues
• Javadocs
• Changelog
  

Documentation 

• Reference documentation
• Screencasts
• SpringSource OSGi blog
  
• HOWTO create a new Spring Dynamic Modules bundle project

Community Contributions

•  Eclipse and Spring-DM intro (PDF)
• OSGi and Enteprise Development
• Agile RCP - Presenter First using Spring Dynamic Modules ( PDF | Sources)
  

Additional Reading

• SpringSource.com: 1.0 Official Press Release
  
•  InfoQ: Spring-DM 1.0 released
• JavaWorld: Introduction to Spring-DM
  

Samples

• Simple Service

Support

• JIRA Issue Tracker
• Forum
  
• Google group

For Developers (trunk snapshot)

Source code repository Javadocs Source code (Fisheye) Submodules reports: Spring OSGi Core Spring OSGi Extender Spring OSGi JUnit support Spring OSGi Mock Committers' Charter Setting up Eclipse for Spring Dynamic Modules development

Maven Repositories

Milestone Repository

Milestone releases (such as 1.0-rc2 or 1.1.0-m1) are deployed at:

<repository>
 <id>spring-maven-milestone</id>
  <name>Springframework Maven Repository</name>
  <url>http://s3.amazonaws.com/maven.springframework.org/milestone</url>
</repository>

Nightly Builds Repository

Nightly snapshot builds are provided for testing and development purposes only. They are built by a Bamboo process automatically using the latest snapshot from Subversion.

The snapshots are deloyed to a Maven2 snapshot repository. To use them, just add the following repository to the POM:

<repository>
 <id>spring-maven-snapshot</id>
  <snapshots><enabled>true</enabled></snapshots>
  <name>Springframework Maven SNAPSHOT Repository</name>
  <url>http://s3.amazonaws.com/maven.springframework.org/snapshot</url>
</repository> 

Individual dependencies can then by added like so:

<dependency>
  <groupId>org.springframework.osgi</groupId>
  <artifactId>spring-osgi-core</artifactId>
  <version>1.0-XXX-SNAPSHOT</version>
</dependency>   

OSGified Artifacts Repository 

OSGified artifacts (such as aopalliance) are provided for development purposes at:

<repository>
 <id>spring-osgified-artifacts</id>
  <snapshots><enabled>true</enabled></snapshots>
  <name>Springframework Maven OSGified Artifacts Repository</name>
  <url>http://s3.amazonaws.com/maven.springframework.org/osgi</url>
</repository> 

Note that the repository is used internally by Spring DM and it is not supported.