Table of Contents
Increasing complexity in modern enterprise applications is a fact of life. You not only have to deal with complex business logic, but also a myriad of other concerns such as security, auditing, exposing business functionality to external applications, and managing the evolution of that functionality and technologies. The Spring Framework and Spring Portfolio products address these needs by offering a Plain-Old Java Object (POJO) based solution that lets you focus on your business logic.
Complex applications pose problems that go beyond using the right set of technologies. You need to take into account other considerations such as a simplified development process, easy deployment, monitoring deployed applications, and managing changes in response to changing business needs. This is where the SpringSource Application Platform comes into play. It offers a simple yet comprehensive platform to develop, deploy, and service enterprise applications. In this Programmer Guide, we explore the runtime portion of the SpringSource Application Platform, the SpringSource dm Server, and learn how to develop applications to benefit from its capabilities.
The SpringSource dm Server requires Java SE 5 or later to be installed. Java is available from Sun and elsewhere.
In this chapter, we provide an overview of the SpringSource dm Server focusing on what it is, what benefits it provides to developers and administrators, and why you should use it.
The SpringSource dm Server, or dm Server for short, is the runtime portion of the SpringSource Application Platform. It is a lightweight, modular, OSGi-based runtime that provides a complete packaged solution for developing, deploying, and managing enterprise applications. By leveraging several best-of-breed technologies and improving upon them, the dm Server offers a compelling solution to develop and deploy enterprise applications.
The SpringSource dm Server is built on top of the following core technologies:
Note, however, that the SpringSource dm Server isn't just a combination of these technologies. Rather, it integrates and extends these technologies to provide many features essential for developing, deploying, and managing today's enterprise Java applications.
The following diagram presents a high-level overview of the dm Server's architecture.
At the heart of the SpringSource dm Server is the SpringSource Dynamic Module Kernel (DMK). The DMK is an OSGi-based kernel that takes full advantage of the modularity and versioning of the OSGi platform. The DMK builds on Equinox and extends its capabilities for provisioning and library management, as well as providing core functionality for the dm Server.
To maintain a minimal runtime footprint, OSGi bundles are installed on demand by the DMK provisioning subsystem. This allows for an application to be installed into a running dm Server and for its dependencies to be satisfied from an external repository. Not only does this remove the need to manually install all your application dependencies, which would be tedious, but it also keeps memory usage to a minimum.
As shown in the figure, SpringSource DMK runs on top of Equinox within a standard Java Virtual Machine. Above the DMK is a layer of subsystems which contribute functionality to the dm Server. Subsystems are configured to run for various profiles and typically provide additional services to the basic OSGi container such as serviceability, management, and personality-specific deployment.
In the SpringSource dm Server, applications are modular and each module has a personality that describes what kind of module it is: web, batch, web service, etc. The dm Server deploys modules of each personality in a personality-specific manner. For example, web modules are configured in Tomcat with web context. Each module in the application can be updated independently of the other modules whilst retaining the identity of being part of the larger application. Whatever kind of application you are building, the programming model remains standard Spring and Spring DM.
Version 1.0.2.RELEASE of the SpringSource dm Server supports the bundle, web, and WAR personalities, which enable you to build sophisticated web applications. The WAR personality includes support for standard Java EE WARs, "shared library" WARs, and "shared services" WARs, each of which will be covered in greater detail in Chapter 4, Deployment Architecture. Future releases will include support for more personalities such as batch, web services, etc.
You could deploy a web application in a stand-alone servlet engine or application server. Or you could even deploy directly in an OSGi container such as Equinox. However, deploying in the SpringSource dm Server offers a number of key benefits that make it both more appealing and more suitable for enterprise application development.
While many applications deployed in the SpringSource dm Server will take advantage of OSGi capabilities, not all applications need such sophistication. For example, development teams may initially choose to continue packaging existing web applications as standard WAR files and then gradually migrate toward a fully OSGi-based packaging and deployment model. The SpringSource dm Server makes such migrations easy for developers by supporting multiple packaging and deployment formats. These formats and migration strategies are discussed in greater detail in Chapter 6, Migrating to OSGi and Chapter 7, Case study: Migrating the Form Tags sample application..
Prior to the release of the SpringSource dm Server, developing and deploying OSGi applications involved inherent complexity such as:
Import-Packagemanifest headers. Many applications use a set of common technologies (e.g., an ORM solution, a web framework, etc.). Combining these two characteristics leads to duplicated configuration in the form of repeated and verbose
Ais comprised of bundles
C. In a standard OSGi environment, if you attempt to install two instances of the same version of application
A(i.e., two sets of bundles
C), a clash will occur, because you cannot deploy multiple bundles with the same
A1is comprised of bundles
C1. Similarly, application
A2is comprised of bundles
C2. Each bundle has a unique combination of
B2both export service
Swhich is imported by both
C2. In contrast to the previous example, there is no conflict resulting from duplicate
Bundle-Versioncombinations; however, there is a clash for the exported service
S. Which service
C2end up using once they are installed? Assuming bundles
C1are intended to work together, you would not want bundle
C1to get a reference to service
B2, because it is installed in a different logical application. On the contrary, you typically want bundle
C1to get a reference to service
Sexported by bundle
B1, but in a standard OSGi environment this may not be the case.
Furthermore, since standard OSGi does not define a notion of an application as a set of bundles, you cannot deploy or undeploy an application and its constituent bundles as a single unit.
The SpringSource dm Server introduces a number of features to solve these issues:
Identifying why an application won't deploy or which particular library dependencies are unsatisfied is the cause of many headaches! Similarly, production time errors that don't identify the root cause are all too familiar to Java developers. The dm Server was designed from the ground up to enable tracing and First Failure Data Capture (FFDC) that empower developers with precise information at the point of failure to fix the problem quickly.
The SpringSource dm Server offers several choices when it comes to deploying applications. Each choice offers certain advantages, and it is important to understand those in order to make the right choice for your application. In this chapter, we take a closer look at the choices offered, compare them, and provide guidelines in choosing the right one based on your specific needs.
The dm Server supports standard self-contained WAR files thus allowing you to use the SpringSource dm Server as an enhanced web server. The dm Server also supports the Shared Libraries WAR format which allows for slimmer WAR files that depend on OSGi bundles instead of including JAR files inside the WAR. The Shared Services WAR format allows developers to further reduce the complexity of standard WARs by deploying services and infrastructure bundles alongside the WAR. A shared services WAR will then consume the services published by those bundles. To complete the picture, the dm Server supports a new OSGi-based Web Module deployment format for web applications that builds on the benefits provided by a shared services WAR and provides additional conveniences for developing and deploying Spring MVC based web applications.
For applications consisting of multiple bundles and web applications, the PAR format is the primary deployment model which takes advantage of OSGi capabilities. We will explore all of these formats and their suitability later in this guide.
The SpringSource dm Server supports applications packaged in the following formats:
When you deploy an application to the dm Server, each deployment artifact (e.g., a single bundle, WAR, or PAR) passes through a deployment pipeline. This deployment pipeline supports the notion of personality-specific deployers which are responsible for processing an application with a certain personality (i.e., application type). The 1.0.2.RELEASE release of the dm Server natively supports personality-specific deployers analogous to each of the aforementioned packaging options. Furthermore, the deployment pipeline can be extended with additional personality deployers, and future releases of the dm Server will provide support for personalities such as Batch, Web Services, etc.
Let's take a closer look now at each of the supported deployment and packaging options to explore which one is best suited for your applications.
At its core, the SpringSource dm Server is an OSGi container. Thus any OSGi-compliant bundle can be deployed directly on the dm Server unmodified. You'll typically deploy an application as a single bundle or a set of stand-alone bundles if you'd like to publish or consume services globally within the container via the OSGi Service Registry.
For Web Application Archives (WAR), the SpringSource dm Server provides support for the following three formats.
Each of these formats plays a distinct role in the incremental migration path from a standard Java EE WAR to an OSGi-ified web application.
Standard WAR files are supported directly in the dm Server. At deployment time, the WAR file is transformed into an OSGi bundle and installed into Tomcat. All the standard WAR contracts are honored, and your existing WAR files should just drop in and deploy without change. Support for standard, unmodified WAR files allows you to try out the SpringSource dm Server on your existing web applications and then gradually migrate toward the Shared Libraries WAR , Shared Services WAR , and Web Module formats.
In addition to the standard support for WARs that you would expect from Tomcat, the dm Server also enables the following features:
Spring-driven load-time weaving (see Section 6.8.4, “Load-time weaving with AspectJ in the Spring Framework").
Diagnostic information such as FFDC (first failure data capture)
The main benefit of this application style is familiarity -- everyone knows how to create a WAR file! You can take advantage of the dm Server's added feature set without modifying the application. The application can also be deployed on other Servlet containers or Java EE application servers.
You may choose this application style if the application is fairly simple and small. You may also prefer this style even for large and complex applications as a starting point and migrate to the other styles over time as discussed in Chapter 6, Migrating to OSGi .
If you have experience with developing and packaging web applications using the standard WAR format, you're
certainly familiar with the pains of library bloat. So, unless you're installing shared libraries in a common
library folder for your Servlet container, you have to pack all JARs required by your web application in
. Prior to the release of the SpringSource dm Server, such library bloat has essentially been the norm for web applications, but
now there is a better solution! The Shared Libraries WAR format reduces your application's deployment footprint and
eradicates library bloat by allowing you to declare dependencies on libraries via standard OSGi manifest headers
. The dm Server provides additional support for simplifying dependency management via the
manifest headers which are essentially macros that get expanded into OSGi-compliant
For detailed information on which libraries are already available, check out the SpringSource Enterprise Bundle Repository .
Once you've begun taking advantage of declarative dependency management with a Shared Libraries WAR, you'll likely
find yourself wanting to take the next step toward reaping further benefits of an OSGi container: sharing services
between your OSGi-compliant bundles and your web applications. By building on the power and simplicity of
Shared Services WAR
format puts the OSGi Service Registry at your finger tips. As a best practice you'll typically publish services
from your domain, service, and infrastructure bundles via
<osgi:service ... />
and then consume them in your web application's ApplicationContext via
<osgi:reference ... />.
Doing so promotes programming to interfaces and allows you to completely decouple your web-specific deployment
artifacts from your domain model, service layer, etc., and that's certainly a step in the right direction. Of the
three supported WAR deployment formats, the Shared Services WAR is by far the most attractive in terms of
modularity and reduced overall footprint of your web applications.
Above and beyond WAR-based deployment formats, the SpringSource dm Server
introduces a deployment and packaging option for OSGi-compliant web applications, the
format. Web modules have a structure similar to a Shared Services WAR and can therefore take full advantage of all
three WAR deployment formats. In addition, web modules benefit from reduced configuration for Spring MVC based
applications via new OSGi manifest headers such as
Web-FilterMappings. For further details on these and other
headers, please consult Section 184.108.40.206, “Web Module Manifest Headers”.
If you're building a Spring MVC based web application as a web module, you won't need to worry about configuring a
WebApplicationContext or an
DispatcherServlet. Based on metadata in your web module's
the dm Server will auto-generate an appropriately configured
for you on-the-fly, and your application will use the ApplicationContext created for your web module by Spring-DM.
Future releases of the dm Server will add additional support to simplify configuration of
Spring Web Flow
based web applications as well.
A PAR is a standard JAR which contains all of the modules of your application (e.g., service, domain, and infrastructure bundles as well as a WAR or web module for web applications) in a single deployment unit. This allows you to deploy, refresh, and undeploy your entire application as a single entity. If you are familiar with Java EE, it is worth noting that a PAR can be considered a replacement for an EAR (Enterprise Archive) within the context of an OSGi container. As an added bonus, modules within a PAR can be refreshed independently and on-the-fly, for example via the SpringSource dm Server Tool Suite (see Chapter 8, Tooling).
Many of the benefits of the PAR format are due to the underlying OSGi infrastructure, including:
Fundamentally modularized applications: instead of relying on fuzzy boundaries between logical modules in a monolithic application, this style promotes physically separated modules in the form of OSGi bundles. Then each module may be developed separately, promoting parallel development and loose coupling.
Robust versioning of various modules: the versioning capability offered by OSGi is much more comprehensive than any alternatives. Each module can specify a version range for each of its dependencies. Bundles are isolated from each other in such a way that multiple versions of a bundle may be used simultaneously in an application.
Improved serviceability: each bundle may be deployed or undeployed in a running application. This allows modifying the existing application to fix bugs, improve performance, and even to add new features without having to restart the application.
Furthermore, PARs scope the modules of your application within the dm Server. Scoping provides both a physical and logical application boundary, effectively shielding the internals of your application from other PARs deployed within the dm Server. This means your application doesn't have to worry about clashing with other running applications (e.g., in the OSGi Service Registry). You get support for load-time weaving, classpath scanning, context class loading, etc., and the dm Server does the heavy lifting for you to make all this work seamlessly in an OSGi environment. If you want to take full advantage of all that the SpringSource dm Server and OSGi have to offer, packaging and deploying your applications as a PAR is definitely the recommend choice.
|OSGi != multiple JARs|
Note that while physically separated modules can, in theory, be implemented simply using multiple JARs, complex versioning requirements often make this impractical. For example, consider the situation depicted in the diagram below.
Suppose that versions 1.0.0 and 2.0.0 of bundle C are neither backward nor forward compatible. Traditional monolithic applications cannot handle such situations: either bundle A or bundle B would need reworking which undermines truly independent development. OSGi's versioning scheme enables this scenario to be implemented in a robust manner. If it is desirable to rework the application to share a single version of C, then this can be planned in and is not forced.
In an OSGi environment, there are two kinds of dependencies between various bundles: type dependency and service dependency.
Type dependency: A bundle may depend on a type exported by another
bundle thus creating a type dependency. Type dependencies are managed through
Export-Package directives in the OSGi manifest. This kind of dependency is similar
to a JAR file using types in other JAR files from the classpath. However, as we've seen earlier, there are
Service dependency: A bundle may also publish services (preferably using Spring-DM), and other bundles may consume those services. If two bundles depend on the same service, both will be communicating effectively to the same object. More specifically, any state for that service will be shared between all the clients of that service. This kind of arrangement is similar to the commonly seen client-server interaction through mechanisms such as RMI or Web Services.
So what makes a good application suitable for deployment on the SpringSource dm Server? Since OSGi is at the heart of the dm Server, modular applications consisting of bundles, which each represent distinct functionality and well-defined boundaries, can take maximum advantage of the OSGi container's capabilities. The core ideas behind forming bundles require following good software engineering practices: separation of concerns, minimum coupling, and communication through clear interfaces. In this section, we look at a few approaches that you may use to create modular applications for SpringSource dm Server deployment. Please consider the following discussion as guidelines and not as rules.
Bundles can be formed along horizontal slices of layering and vertical slices of function. The objective is to enable independent development of each bundle and minimize the skills required to develop each bundle.
For example, an application could have the following bundles: infrastructure, domain, repository, service, and web as shown in the following diagram.
Each bundle consists of types appropriate for that layer and exports packages and services to be used by other layers. Let's examine each bundle in more details:
Table 4.1. Bundles across layers
|Bundles||Imported Packages||Exported Packages||Consumed Services||Published Services|
|Infrastructure||Third-party libraries||Infrastructure interfaces||None||None|
|Domain||Depends: for example, if JPA is used to annotate persistent types, then JPA packages.||Public domain types||None||None|
|Web||Domain, Service||None||Service beans||None|
|Service||Domain, Infrastructure, Repository||Service interfaces||Repository beans||Service beans|
|Repository||Domain, Third-party libraries, ORM bundles, etc.||Repository interfaces||DataSources, ORM session/entity managers, etc.||Repository beans|
Within each layer, you may create bundles for each subsystem representing a vertical slice of business functionality. For example, as shown in the following figure, the service layer is divided into two bundles each representing separate business functionalities.
You can similarly separate the repositories, domain classes, and web controllers based on the business role they play.
Applications that take advantage of the OSGi capabilities of the SpringSource dm Server are typically comprised of multiple bundles. Each bundle may have dependencies on other bundles. Furthermore, each bundle exposes only certain packages and services. In this chapter, we look at how to create bundles, import and export appropriate functionality, and create artifacts to deploy web applications on the SpringSource dm Server.
This is an abbreviated introduction to OSGi bundles. Please refer to the Spring Dynamic Modules for OSGi documentation for full details.
An OSGi bundle is simply a jar file with metadata that describe additional characteristics such as version and imported and exported packages.
A bundle exports types and publishes services to be used by other bundles:
via the OSGi
<service ... /> XML namespace element.
A bundle may import types and services exported by other bundles:
via the OSGi
<reference ... /> XML namespace element.
Let's see an example from the PetClinic sample application. The following listing shows the
MANIFEST.MF file for the
Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: PetClinic HSQL Database Infrastructure Bundle-SymbolicName: org.springframework.petclinic.infrastructure.hsqldb Bundle-Version: 1.0 Bundle-Vendor: SpringSource Inc. Import-Library: org.springframework.spring;version="[2.5,2.6]" Import-Bundle: com.springsource.org.apache.commons.dbcp;version="[1.2.2.osgi,1.2.2.osgi]", com.springsource.org.hsqldb;version="[220.127.116.11,18.104.22.168]" Import-Package: javax.sql Export-Package: org.springframework.petclinic.infrastructure
org.springframework.petclinic.infrastructure.hsqldb bundle expresses its dependencies on
javax.sql package, the Commons DBCP and HSQLDB bundles, and the Spring library (we will examine
the details of the library artifact in Section 5.5.3, “Defining libraries”). The Commons DBCP
bundle is imported at a version of exactly 1.2.2.osgi and the HSQLDB bundle is imported at a version of exactly
22.214.171.124. The Spring library is imported at a version between 2.5 inclusive and 2.6 exclusive.
Note that you do not specify the bundle that will provide the imported packages. The SpringSource dm Server will examine the available bundles and satisfy the required dependencies.
osgi-context.xml file from the PetClinic sample's
org.springframework.petclinic.repository.jdbc bundle declares a service published by the bundle and
references a service published by another bundle.
<?xml version="1.0" encoding="UTF-8"?> <beans:beans xmlns="http://www.springframework.org/schema/osgi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:beans="http://www.springframework.org/schema/beans" xsi:schemaLocation="http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osgi.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <service id="osgiClinic" ref="clinic" interface="org.springframework.petclinic.repository.Clinic" /> <reference id="dataSource" interface="javax.sql.DataSource"/> </beans:beans>
service element publishes the
(a regular Spring bean declared in the
module-context.xml file) and specifies
org.springframework.petclinic.repository.Clinic as the type
of the published service.
reference elements define a
dataSource bean that references
a service published by another bundle with a an interface type of
The SpringSource dm Server supports two OSGi-oriented ways of packaging applications: the PAR format and application modules (including personality-specific modules). The dm Server also supports three distinct WAR deployment and packaging formats: standard Java EE WAR, Shared Libraries WAR, Shared Services WAR.
An OSGi application is packaged as a JAR file, with extension
.par. A PAR artifact offers several benefits:
A PAR includes one or more application bundles and its manifest specifies the following manifest headers:
Table 5.1. PAR file headers
|Identifier for the application which, in combination with Application-Version, uniquely identifies an application|
|Human readable name of the application|
|Version of the application|
|Short description of the application|
The following code shows an example MANIFEST.MF in a PAR file:
Application-SymbolicName: com.example.shop Application-Version: 1.0 Application-Name: Online Shop Application-Description: Example.com's Online Shopping Application
A module offers OSGi-oriented packaging that supports specific application personalities.
In this release, the only supported application personality is "
The most common type of application deployed in the SpringSource dm Server is, not surprisingly, the web application. The dm Server, therefore, supports the concept of a Web Module. A Web module is an OSGi bundle whose manifest includes directives to support various options pertinent to a web application.
Web modules have the following advantages over standard Java EE WAR files:
Dependencies can be referenced rather than bundled in
Dependencies are accessed via an export signature and so their internals can be controlled.
External dependencies can be installed once, thus reducing the overall footprint and deployment overhead of the web module.
Web modules have explicit identifying metadata and so can be handled straightforwardly as exploded directories.
Web modules are OSGi bundles and so can benefit from dynamic updates, fragment attachment for I18N, etc.
Web modules are Spring-DM powered.
Web modules are standard OSGi bundles with the following characteristics:
Packaged as an OSGi bundle with a
.jar extension, either stand-alone or within a PAR.
Required bundle manifest headers:
Optional bundle manifest headers (see Web Module Manifest Headers).
A web module must publish an
via standard Spring-DM extender semantics (e.g., /META-INF/spring/*.xml).
This application context will actually be an OSGi-aware implementation of
In addition, this application context will be used as the
DispatcherServlet which will be automatically configured.
Thus, the context configuration files loaded by Spring-DM must contain all web related
components (e.g., Spring MVC Controllers, Filters, SWF, Spring Security, etc.).
There is no need for a
WEB-INF/<dispatcher servlet name>-servlet.xml, because:
DispatcherServletwill be automatically configured to use the
WebApplicationContextcreated by Spring-DM for the web module
web.xmldeployment descriptor, since an appropriate
web.xmlwill be automatically generated for the web module based on the supplied web module manifest headers. When manifest headers alone do not suffice, however, a web module may be configured via a
web.xmlfragment which will be merged with any automatically generated elements. For further details, consult the discussion on web.xml fragments later in this chapter.
New OSGi-centric web application directory structure.
For web modules, any artifacts which would typically reside in the root of a
standard WAR are placed in a special directory called
which resides in the root of the bundle. This directory serves as the root of the
ServletContext and thus provides a central location for artifacts
which should be publicly accessible via standard HTTP requests (e.g., images, CSS files
MODULE-INF is also
the directory in which you should place
WEB-INF and related subdirectories
Public web resources:
Web resources which are intended to be publicly visible via HTTP requests should
be packaged underneath
/MODULE-INF. This is analogous to the root of a
standard Java EE WAR and excludes anything packaged underneath
Private web resources:
Consistent with standard Java EE WAR deployments, web resources which are not
intended to be publicly visible via HTTP requests should be packaged
/MODULE-INF/WEB-INF, for example: JSP fragments, templates,
configuration files, etc.
Classes: For consistency with raw OSGi bundles, Java classes (i.e., .class files) and packages should typically be packaged in the root of the bundle.
For backwards compatibility with the standard WAR format, Java classes may be packaged
Class-path resources: Class-path resources such as properties files, XML configuration files, etc. should also be packaged in the root of the bundle.
Any third-party libraries (i.e., JARs) used by your web application which are not referenced
via the dm Server's repository using
should be packaged in root of the bundle and added to the
For backwards compatibility with the standard WAR format, third-party libraries
may be packaged in
For Web Modules, the SpringSource dm Server introspects the contents of the deployed artifact and
Web modules support the following manifest headers for configuring the bundle's web application.
Table 5.2. Web module manifest headers
Used to configure the unique context path under which the web module or WAR is deployed in the Servlet Container.
Syntax: standard Servlet syntax rules for context paths apply.
To deploy a web application as the root context, supply a context path
consisting of a single forward slash,
|The module's file name minus the extension.|
Used to declare a
Syntax: comma-separated list of (note: white space added for legibility):
Used for mapping request URLs to the auto-configured
Syntax: comma-separated list of
Let's take a look at the use of these headers in an example:
Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-SymbolicName: org.springframework.showcase.formtags Bundle-Version: 2.0.8 Bundle-Name: Spring Form Tags - Sample Web Application Bundle-Description: Sample web application which demonstrates the use of Spring 2.0's custom form tag library Import-Package: org.springframework.osgi.web.context, org.springframework.osgi.web.servlet, org.springframework.showcase.formtags.domain;version="2.0.8", org.springframework.showcase.formtags.service;version="2.0.8", org.springframework.showcase.formtags.validation;version="2.0.8", org.springframework.showcase.formtags.web;version="2.0.8" Import-Library: org.springframework.spring;version="2.5.4" Module-Type: Web Web-ContextPath: formtags Web-DispatcherServletUrlPatterns: *.htm Web-FilterMappings: securityFilter;url-patterns:="*.htm,*.jsp", imageFilter;url-patterns:="/image/*"
In addition to the aforementioned
Web-* manifest headers, the SpringSource dm Server
also supports configuration of web modules via
If necessary, a web module may contain an existing
fragment which will be merged with the automatically generated elements.
Such fragments allow developers to configure web.xml in ways that are not supported by web manifest
headers alone, thus providing greater flexibility as well as the full feature set of web.xml
To use a web.xml fragment, simply configure
/MODULE-INF/WEB-INF/web.xml as you normally would
for a standard Java EE WAR. Then, if there are elements that you wish to be auto-configured for your
web module -- for example, an auto-configured
element -- configure those via
Web-* manifest headers (e.g.,
and the elements in the provided web.xml fragment will then be merged with the auto-configured elements.
The following three listings demonstrate how
Web-* manifest headers and a
web.xml fragment can be combined to configure a version of the Form Tags show case application's
web module. The first listing displays the web module's
Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-SymbolicName: formtags-web Bundle-Version: 2.0.8 Import-Package: org.springframework.showcase.formtags.domain;version=" 2.0.8",org.springframework.showcase.formtags.service;version="2.0.8", org.springframework.showcase.formtags.validation;version="2.0.8",org. osgi.framework,org.springframework.osgi.context Import-Library: org.springframework.spring;version="2.5.4" Module-Type: Web Web-ContextPath: formTagsParWithWebModuleAndWebXmlFragment Web-DispatcherServletUrlPatterns: *.htm
The second listing displays the
/MODULE-INF/WEB-INF/web.xml fragment for the
<?xml version="1.0" encoding="ISO-8859-1"?> <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> <display-name>Spring Form Tags - Sample Web Application</display-name> <description> Sample web application which demonstrates the use of Spring 2.0's custom form tag library </description> <filter> <filter-name>imageFilter</filter-name> <filter-class>com.example.filter.ImageFilter</filter-class> </filter> <filter-mapping> <filter-name>imageFilter</filter-name> <url-pattern>/images/*</url-pattern> </filter-mapping> <session-config> <session-timeout>5</session-timeout> </session-config> <welcome-file-list> <welcome-file>index.jsp</welcome-file> <welcome-file>index.htm</welcome-file> </welcome-file-list> </web-app>
The third listing displays the resulting merged
deployment descriptor with which the web application will be deployed on the dm Server.
<?xml version="1.0" encoding="ISO-8859-1"?> <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> <servlet> <servlet-name>formtags-web-DispatcherServlet</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> <load-on-startup>2</load-on-startup> <init-param> <param-name>contextAttribute</param-name> <param-value>formtags-web-ApplicationContext</param-value> </init-param> </servlet> <servlet-mapping> <servlet-name>formtags-web-DispatcherServlet</servlet-name> <url-pattern>*.htm</url-pattern> </servlet-mapping> <display-name>Spring Form Tags - Sample Web Application</display-name> <description> Sample web application which demonstrates the use of Spring 2.0's custom form tag library </description> <filter> <filter-name>imageFilter</filter-name> <filter-class>com.example.filter.ImageFilter</filter-class> </filter> <filter-mapping> <filter-name>imageFilter</filter-name> <url-pattern>/images/*</url-pattern> </filter-mapping> <session-config> <session-timeout>5</session-timeout> </session-config> <welcome-file-list> <welcome-file>index.jsp</welcome-file> <welcome-file>index.htm</welcome-file> </welcome-file-list> </web-app>
As you can see in the above listing, the SpringSource dm Server processes the
Web-* manifest headers in the web module's
/META-INF/MANIFEST.MF file, auto-generates the
necessary web.xml elements -- which are configured to access the web
module's Spring-DM powered
and inserts the auto-generated elements into the merged deployment
descriptor. The results of the auto-generation process are then merged
with the elements supplied in the
When packaging WARs for deployment on the SpringSource dm Server, the following should serve as general guidelines.
Context Path: As with web modules, the
unique context path under which a WAR is deployed
in the Servlet Container can be configured via the
manifest header. If no context path is explicitly configured, the file name
of the WAR minus the
.war extension will be used by
Standard Java EE WAR: you can deploy a standard WAR "as is" on the dm Server. There is typically no need to modify it in any way.
Shared Libraries WAR: a Shared Libraries WAR has exactly
the same structure as a standard WAR. The only difference is that shared libraries, which were
previously stored in
/WEB-INF/lib or in a centralized location for
the Servlet container, are now installed in the dm Server as OSGi bundles and referenced
Shared Services WAR: in terms of packaging and the physical
structure of the deployment artifact, everything that applies to a Shared Libraries WAR
equally applies to a Shared Services WAR. To enable service lookup from a Spring MVC based
web application, however, you will need to configure an OSGi-enabled
WebApplicationContext in your WAR's
deployment descriptor. The SpringSource dm Server provides the
which is suited exactly for this purpose. The following code listing demonstrates how to
ServerOsgiBundleXmlWebApplicationContext for your
<context-param> <param-name>contextClass</param-name> <param-value>com.springsource.server.web.dm.ServerOsgiBundleXmlWebApplicationContext</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener>
The recommended approach for interacting with the OSGi Service Registry in
a Shared Services WAR is to use Spring-DM's
<osgi:reference ... />
and related XML namespace elements but to limit such usage to your root
WebApplicationContext. It is therefore not typically recommended that
you interact with the OSGi Service Registry, for example, from within a
WebApplicationContext for a particular
If necessary, however, you may also configure a Spring MVC
to create an OSGi-enabled
WebApplicationContext as follows.
<servlet> <servlet-name>dispatcherServlet</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> <init-param> <param-name>contextClass</param-name> <param-value>com.springsource.server.web.dm.ServerOsgiBundleXmlWebApplicationContext</param-value> </init-param> </servlet>
Module personalities typically provide automatic access to features specific to the personality via custom manifest headers or other configuration mechanisms. There may be situations, however, for which programmatic access to such features is desirable or necessary. This section describes how to programmatically access personality-specific features from application code in a module.
The SpringSource dm Server automatically creates a
for Web Modules and appropriately configured Shared Services WARs which
have Spring-DM powered
ApplicationContext XML configuration files.
For Web Modules in particular, a
will be created which is typically used in conjunction with
an auto-configured Spring MVC
In such scenarios, there is generally no need to access the
since all components of the web application are configured
within the scope of the
itself. For Shared Services WARs, or for Web Modules which do
not directly rely on Spring MVC, you can alternatively access
the Spring-DM powered
via the web application's
The Web Personality subsystem stores the bundle's
WebApplicationContext in the ServletContext under
the attribute name "
BSN is the
of your Shared Services WAR or Web Module. Thus, for a Web Module,
you can use Spring MVC's WebApplicationContextUtils'
method (or other means) to programmatically retrieve a reference to the
WebApplicationContext, which is an instance
For Shared Services WARs, you can programmatically retrieve
WebApplicationContext directly from the
Alternatively, since the Web Personality subsystem also stores the
WebApplicationContext under the attribute name
with the value of the
constant, you may choose to use Spring MVC's WebApplicationContextUtils'
methods to access the
WebApplicationContext without providing
an explicit attribute name.
Similar to programmatic access to the
as described above, you can access the
of your Shared Services WAR or Web Module via the web application's
ServletContext. The Web Personality subsystem
stores the bundle context under the attribute name with the value of the
The SpringSource dm Server generates automatic package imports (e.g., via the
Import-Package manifest header) for various
module personalities. This section lists which packages are automatically
generated for each personality.
All deployment artifacts supported by the Web personality (i.e.,
all WAR variants and Web Modules) will have the following
packages automatically added to their bundle manifest via
In addition, to ensure compatibility for existing, standard Java EE WARs,
the dm Server automatically imports all packages exported by the
OSGi system bundle, excluding any packages which begin with
org.eclipse" or "
The resulting set of filtered system bundle exports will be
automatically imported for all WAR variants but not for Web Modules;
however, for all web deployment artifacts it is recommended that all known
dependencies be explicitly specified in
via the appropriate
|System Bundle Package Exports|
For further details on which packages are exported by the
OSGi system bundle, consult the
Complex enterprise frameworks such a Spring and Hibernate are typically divided into many, many different packages. Traditionally, if an OSGi bundle wished to make extensive use of such a framework its manifest would have to import a huge number of different packages. This can be an error-prone and tedious process. Furthermore, application developers are used to thinking in terms of their application using a framework, such as Spring, as a whole, rather than a long list of all the different packages that comprise the framework.
The following figure provides a simple illustration of the complexity of only using
The SpringSource dm Server reduces the need for long lists of imported packages by introducing two new manifest
Import-Library. The following figure provides an
illustration of the simplification that these new headers offer:
As you can see, use of
Import-Library can lead to a dramatic reduction
in the number of imports that you need to include in an application bundle's manifest. Furthermore,
Import-Library are simply aliases for
Import-Package; at deployment time
Import-Library header entries are automatically expanded into numerous
Import-Package entries. This
means that you retain the exact same semantics of using
Import-Package, without having to go through the labourious
process of doing so.
A bundle in an application can declare a dependency on a library by using the
SpringSource dm Server-specific
Import-Library header. This header specifies a
comma-separated list of library symbolic names and version ranges that determine which libraries
are imported. By default a dependency on a library is mandatory but this can be
controlled through use of the resolution directive in exactly the same way as
it can with
Import-Library: org.springframework.spring;version="[2.5.4, 3.0)", org.aspectj;version="[1.6.0,1.6.0]";resolution:="optional"
Import-Library header declares a mandatory dependency on the Spring
library at a version from 2.5.4 inclusive to 3.0 exclusive. It also declares an
optional dependency on the AspectJ library at exactly 1.6.0.
A bundle in an application can declare a dependency on a bundle by using the
SpringSource dm Server-specific
Import-Bundle header. The header specifies a comma-separated
list of bundle symbolic names and version ranges that determine which bundles are imported. By default a dependency
on a bundle is mandatory but this can be controlled through use of the resolution directive in exactly
the same way as it can with
Import-Bundle: com.springsource.org.apache.commons.dbcp;version="[1.2.2.osgi, 1.2.2.osgi]"
Import-Bundle header declares a mandatory dependency on the Apache Commons
DBCP bundle at exactly 1.2.2.osgi.
Libraries are defined in a simple text file, typically with a
.libd suffix. This file identifies the
library and lists all of its constituent bundles. For example, the following is the library definition for
Library-SymbolicName: org.springframework.spring Library-Version: 2.5.4 Library-Name: Spring Framework Import-Bundle: org.springframework.core;version="[2.5.4,2.5.5)", org.springframework.beans;version="[2.5.4,2.5.5)", org.springframework.context;version="[2.5.4,2.5.5)", org.springframework.aop;version="[2.5.4,2.5.5)", org.springframework.web;version="[2.5.4,2.5.5)", org.springframework.web.servlet;version="[2.5.4,2.5.5)", org.springframework.jdbc;version="[2.5.4,2.5.5)", org.springframework.orm;version="[2.5.4,2.5.5)", org.springframework.transaction;version="[2.5.4,2.5.5)", org.springframework.context.support;version="[2.5.4,2.5.5)", org.springframework.aspects;version="[2.5.4,2.5.5)", com.springsource.org.aopalliance;version="1.0"
The following table lists all of the headers that may be used in a library definition:
Table 5.3. Library definition headers
|Library-SymbolicName||Identifier for the library|
|Library-Version||Version number for the library|
|Import-Bundle||A comma separated list of bundle symbolic names, each may optionally specify a version|
|Library-Name||Optional. The human-readable name of the library|
|Library-Description||Optional. A human-readable description of the library|
Rather than encouraging the packaging of all an application's dependencies within the application itself, SpringSource dm Server uses a local provisioning repository of bundles and libraries upon which an application can depend. When the SpringSource dm Server encounters an application with a particular dependency, it will automatically provide, from its provisioning repository, the appropriate bundle or library.
Making a dependency available for provisioning is simply a matter of copying it to the appropriate location in the
dm Server's local provisioning repository. By default this is
SERVER_HOME/repository/bundles/usr for bundles, and
SERVER_HOME/repository/libraries/usr for libraries. A more detailed discussion of the provisioning
repository can be found in the User Guide.
As described in the User Guide SpringSource dm Server provides support for
per-application trace. SpringSource dm Server provides SLF4J-based implementations of both Commons Logging and Log4J which allow
trace generated by applications using those APIs to be captured and included in the application trace file. This use of
SLF4J-based replacement implementations means that the standard configuration mechanisms for Commons Logging and Log4J
cannot be used. Instead, application trace is configured via the use of the
header in the application's manifest as described in the User Guide.
If you do not wish to take advantage of the SpringSource dm Server's built-in support for per-application trace, it is possible to force your application to utilise vanilla Log4J rather than the SLF4J-based implementation that is provided in the SpringSource dm Server. This can be achieved by specifying the bundle symbolic name of the vanilla Log4J bundle when importing the Log4J package in your application's manifests. E.g.:
In much the same way that individual OSGi bundles can be versioned, SpringSource dm Server allows applications to be versioned. This is
achieved by using the
Application-Version manifest header, in the case of a multi-bundle application packaged
as a PAR file, or by using the
Bundle-Version manifest header, in the case of a single-bundle application.
SpringSource dm Server uses an application's version to prevent clashes when multiple versions of the same application are deployed at the same time. For example, the application trace support described in Section 5.6, “Application trace”, includes the application's name and version in the trace file path. This ensures that each version of the same application has its own trace file.
Taking on a new technology such as OSGi may seem a bit daunting at first, but a proven set of migration steps can help ease the journey. Teams wishing to migrate existing applications to run on the SpringSource dm Server will find that their applications typically fall into one of the following categories.
Web Application: for web applications, this chapter provides an overview of the steps required to migrate from a Standard WAR to a Web Module. Furthermore, the following chapter provides a detailed case study involving the migration of the Spring 2.0 Form Tags show case application.
Anything else: for any other type of application, you will typically either deploy your application as multiple individual bundles or as a single PAR, which is the recommended approach for deploying applications on the SpringSource dm Server. See Section 6.2, “PAR” for details on migrating to a PAR.
Many applications may start with the standard WAR format for web applications and gradually migrate to a more OSGi-oriented architecture. Since the SpringSource dm Server offers several benefits to all supported deployment formats, it provides a smooth migration path. Of course, depending on your application's complexity and your experience with OSGi, you may choose to start immediately with an OSGi-based architecture.
If you are not yet familiar with OSGi or simply want to deploy an existing web application on the SpringSource dm Server, you can deploy a standard WAR and leverage the dm Server with a minimal learning curve. In fact reading the SpringSource dm Server User Guide is pretty much all that you need to do to get started. Furthermore, you will gain familiarity with the SpringSource dm Server, while preparing to take advantage of the other formats.
The Shared Libraries WAR format is the first step to reaping the benefits of OSGi. In this phase, you dip your toes into OSGi-based dependency management by removing JAR files from the WAR and declaring dependencies on corresponding OSGi bundles.
In this phase, you take the next step toward a fully OSGi-based architecture by separating your web artifacts (e.g., Servlets, Controllers, etc.) from the services they depend on.
The final step in migrating a WAR is to convert it to a Web Module. As mentioned in Section 4.1.3, “Web Modules”, this format has a structure similar to that of a Shared Services WAR and adds additional benefits of reduced configuration for Spring MVC based applications via new OSGi manifest headers.
The following diagram graphically depicts the migration path from a Standard WAR to a Web Module. As you can see, the libraries (libs) move from within the deployment artifact to the Bundle Repository. Similarly, the services move from within the WAR to external bundles and are accessed via the OSGi Service Registry. In addition, the overall footprint of the deployment artifact decreases as you move towards a Web Module.
When migrating an existing application to the PAR packaging and deployment format, you consider modularity as the prime objective. Following the ideas discussed in Section 4.3, “A guide to forming bundles”, you refactor the application into multiple bundles. You may start conservatively with a small number of bundles and then further refactor those bundles.
If the original code is crafted following good software practices such as separation of concerns and use of well-defined interfaces, migration may involve modifying only configuration and packaging. In other words, your Java sources will remain unchanged. Even configuration is likely to change only slightly.
For example, the following diagram depicts a typical web application that has been refactored and
packaged as a PAR. The blue elements within the Application box constitute
the bundles of the application. Each of these bundles imports types from other bundles within
the PAR using
Import-Package. The green elements in the left column represent
libraries installed on the dm Server. The PAR's bundles reference these
Import-Library. The purple element in the left column
represents a bundle within the dm Server's bundle repository which is imported by the DAO
Import-Bundle. In contrast to a traditional, monolithic
WAR deployment, the PAR format provides both a logical and physical application boundary
and simultaneously allows the application to benefit from both the OSGi container and
the SpringSource dm Server.
In this chapter we will walk through the steps needed to migrate the Form Tags sample application from a standard Java EE WAR to a fully OSGi compliant web module within a PAR. The migration involves four packaging and deployment formats:
Each of these migration steps will produce a web application that can be deployed and run on the dm Server.
The following image displays the directory structure you should have
after installing the Form Tags sample. Note however that the release tag
will typically resemble
dist directory contains the distributables,
projects directory contains the source code
and build scripts.
For simplicity, this chapter will focus on the distributables -- which are built using Spring-Build -- rather than on configuring a project in an IDE.
Pre-packaged distributables are made available in the |
The sample that we will be using is the Form Tags show case sample which was provided with Spring 2.0. The Form Tags application has been removed from the official Spring 2.5.x distributions; however, since it is relatively simple but still contains enough ingredients to demonstrate the various considerations required during a migration, we have chosen to use it for these examples.
The purpose of the Form Tags show case sample was to demonstrate how
the Spring specific
form: tags, released
in Spring 2.0, make view development with JSPs and tag libraries easier.
The Form Tags application consists of a single
UserService which returns a list
Users. Furthermore, the application demonstrates how to list, view,
Users in a simple Spring MVC based web application using JSP
We begin with a standard WAR deployment.
|The SpringSource dm Server supports the standard Java EE WAR packaging and deployment format as a first-class citizen, and there are many benefits to deploying a standard WAR file on the dm Server including, but not limited to: tooling support, runtime error diagnostics, FFDC (i.e., first failure data capture), etc. In addition, support for standard WAR deployment provides an easy on-ramp for trying out the SpringSource dm Server with existing web applications.|
The following screen shot displays the directory structure of the
Form Tags application using the standard WAR format. As you can see,
there is no deviation from the standard structure and layout, and as
you would expect, all of the web application's third-party dependencies
(e.g., Spring. Commons Logging, etc.) are packaged as JARs in
To deploy this application, simply copy
SERVER_HOME/pickup directory for hot deployment.
You should then see the dm Server produce console output similar to the following:
The console output has been reformatted to fit this document.
[2008-05-13 13:19:30.972] fs-watcher <SPSC1000I> Creating web application '/formtags-war-1.0.0.RELEASE'. [2008-05-13 13:19:31.045] async-delivery-thread-1 <SPSC1001I> Starting web application '/formtags-war-1.0.0.RELEASE'. [2008-05-13 13:19:31.697] fs-watcher <SPDE0010I> Deployment of 'formtags-war-1.0.0.RELEASE.war' version '0' completed.
http://localhost:8080/ plus the web application context path,
which in the above case is
formtags-war-1.0.0.RELEASE. Thus navigating to
should render the sample application's welcome page, as displayed in the screen
For WARs, the default web context path is the name of the WAR file
without the |
As mentioned above, a standard WAR file typically packages of all its required
WEB-INF/lib. The servlet container will
then add all of the JARs in
WEB-INF/lib to the application's
The first step of the migration towards benefiting from an OSGi container is to continue using a WAR but retrieve the dependencies from the dm Server's bundle repository at runtime. This can significantly reduce the time it takes to build and deploy the application. It also enables the enforcement of policies regarding the use of third-party libraries.
The way in which dependencies are declared in an OSGi environment is
via manifest headers in a bundle's
As mentioned in Chapter 5, Developing Applications, there are
three ways of expressing dependencies:
The Form Tags application uses JSTL standard tag libraries.
Thus, you need to choose a JSTL provider, for example the
Apache implementation which comes with the dm Server. To use the
Apache implementation of JSTL, you need to express your dependency
as outlined in the following manifest listing.
Because it is a single bundle,
the simplest and therefore preferred manifest header to use.
The Form Tags application requires commons-logging and Spring.
It would be very painful to have to list all the Spring packages one by one.
Equally, considering the number of bundles that make up the
Spring framework, it would be verbose to list each bundle. Therefore
Import-Library is the preferred approach
for expressing the dependency on the Spring framework.
How do you determine the name of a library definition provided by the SpringSource dm Server? Use the SpringSource Enterprise Bundle Repository.
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 1.5.0_13-119 (Apple Inc.) Bundle-ManifestVersion: 2 Bundle-SymbolicName: org.springframework.showcase.formtags-shared-libs Bundle-Vendor: SpringSource Inc. Import-Library: org.springframework.spring;version="[2.5.4,3.0.0)" Import-Bundle: com.springsource.org.apache.taglibs.standard;version="1 .1.2"
You can see the
directives that instruct the dm Server to add the appropriate package imports to the bundle
classpath used by this WAR file.
Deploying the shared libraries WAR onto the dm Server should result in console output similar to the following:
The console output has been reformatted to fit this document.
[2008-05-13 13:23:00.520] fs-watcher <SPSC1000I> Creating web application '/formtags-shared-libs-1.0.0.RELEASE'. [2008-05-13 13:23:00.524] async-delivery-thread-1 <SPSC1001I> Starting web application '/formtags-shared-libs-1.0.0.RELEASE'. [2008-05-13 13:23:00.894] fs-watcher <SPDE0010I> Deployment of 'formtags-shared-libs-1.0.0.RELEASE.war' version '0' completed.
should render the welcome page. Note that for the pre-packaged distributable,
BUILDTAG should be similar to
whereas, for a local build the
-BUILDTAG may be completely
omitted. Please consult the console output, web-based admin console, or log
to determine the exact context path under which the web application has been deployed.
The next step in the migration is to deploy the services as a separate
OSGi bundle which the WAR then references.
The Form Tags sample has a single service
This scenario has two separate deployables, the
service bundle and the WAR file.
The following image shows the two separate source trees:
|Note that the WAR does not contain the |
The responsibility of the first bundle (
is to provide the API of the formtags service. This includes both the
domain and the service API. In the same way that imports are defined
/META-INF/MANIFEST.MF, so are exports.
The following is the
/META-INF/MANIFEST.MF listing from the service bundle.
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 1.5.0_13-119 (Apple Inc.) Bundle-ManifestVersion: 2 Bundle-Name: FormTags Service (and implementation) Bundle-SymbolicName: org.springframework.showcase.formtags.service-sha red-services Bundle-Vendor: SpringSource Inc. Export-Package: org.springframework.showcase.formtags.service,org.spri ngframework.showcase.formtags.domain Import-Library: org.springframework.spring;version="[2.5.4,3.0.0)" Bundle-Version: 1.0.0.BUILD-20080509155958
The symbolic name of this bundle is
Note that the name of the bundle typically describes the package
that the bundle primarily exports.
If you take a look at the
repository/bundles/ext in the dm Server
directory, you'll see that names are almost always indicative of the contents of the bundle.
For this example, however, we have also appended
in order to avoid possible clashes with other bundle symbolic names.
You will see later that the PAR also contains a service bundle.
In OSGi, the combination of |
As well as exporting types (i.e. the domain classes and service
API), the service bundle also publishes an implementation of the
UserManager. The actual implementation is
StubUserManager; however, that should remain an
implementation detail of this bundle.
The fact that this bundle publishes a service is not captured in
/META-INF/MANIFEST.MF, as it is a Spring-DM concept.
The following image is of
As you can see there are two Spring configuration files:
These names are abitrary; however, they follow an informal convention:
The following is a listing of
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd"> <bean id="userManager" class="org.springframework.showcase.formtags.service.internal.StubUserManager"/> </beans>
As you can see, this simply defines a bean called
The following is a listing of
<?xml version="1.0" encoding="UTF-8"?> <beans:beans xmlns="http://www.springframework.org/schema/osgi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:beans="http://www.springframework.org/schema/beans" xsi:schemaLocation="http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osgi.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <service ref="userManager" interface="org.springframework.showcase.formtags.service.UserManager"/> </beans:beans>
This single bean definition exports the
module-context.xml to the
OSGi service registry and makes it available under the public
The service bundle should now be ready to deploy on the dm Server.
Output similar to the following should appear in the dm Server's console:
The console output has been reformatted to fit this document.
[2008-05-13 13:25:49.415] fs-watcher <SPDE0010I> Deployment of 'formtags-shared-services-service-1.0.0.RELEASE.jar' version '0' completed.
The WAR file now needs to access the types and service exported
by the service bundle. The following listing is the WAR's
/META-INF/MANIFEST.MF which imports the types
exported by the service bundle. The
statement has also been extended to import
which is necessary in order to load an OSGi-enabled
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 1.5.0_13-119 (Apple Inc.) Bundle-ManifestVersion: 2 Bundle-SymbolicName: org.springframework.showcase.formtags.web-shared- services Bundle-Vendor: SpringSource Inc. Import-Package: org.springframework.showcase.formtags.domain,org.sprin gframework.showcase.formtags.service Import-Library: org.springframework.spring;version="[2.5.4,3.0.0)" Import-Bundle: com.springsource.org.apache.taglibs.standard;version="1 .1.2",org.springframework.osgi.core
In addition to importing the exported types of the service bundle,
the WAR must also obtain a reference to the
published by the service bundle. The following image shows the directory
structure of the Shared Services WAR.
As you can see in the above image, the Form Tags Shared Services WAR's
/WEB-INF/web.xml directory contains a standard
applicationContext.xml which defines the configuration
for the root
formtags-servlet.xml which defines the configuration specific to the
As is typical for Spring MVC based web applications, you configure a
web.xml to load your root
WebApplicationContext; however, to enable your
WebApplicationContext to be able to reference services from the OSGi Service Registry,
you must explicitly set the
contextClass Servlet context parameter to the fully qualified
class name of a
ConfigurableWebApplicationContext which is OSGi-enabled. When deploying
Shared Services WARs to the SpringSource dm Server, you should use
com.springsource.server.web.dm.ServerOsgiBundleXmlWebApplicationContext. This will
then enable the use of Spring-DM's
<reference ... /> within your root
WebApplicationContext (i.e., in
The following listing is an excerpt from
<context-param> <param-name>contextClass</param-name> <param-value>com.springsource.server.web.dm.ServerOsgiBundleXmlWebApplicationContext</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener>
The Form Tags Shared Services WAR contains a
file which is the default configuration location used to create the root
WebApplicationContext for Spring MVC's
As already mentioned, in the OSGi world, bundle configuration
takes place in the root |
The following is the listing of the WAR's
<?xml version="1.0" encoding="UTF-8"?> <beans:beans xmlns="http://www.springframework.org/schema/osgi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:beans="http://www.springframework.org/schema/beans" xsi:schemaLocation="http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osgi.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <reference id="userManager" interface="org.springframework.showcase.formtags.service.UserManager"/> </beans:beans>
The single bean declaration is retrieving a service that implements
API from the OSGi Service Registry.
|You might have been expecting a reference to the service bundle, but that isn't how OSGi works. OSGi provides a service registry, and this bean definition is accessing a service in that registry that meets the specified restriction (i.e. implements the specified interface). This leads to a very loosely coupled programming model: the WAR really doesn't care where the implementation comes from.|
|What happens if there is no service at runtime? What if there are multiple services that match the criteria? Spring-DM provides a lot of configuration options, including whether or not the reference is mandatory, how long to wait for a service reference, etc. Please consult the Spring Dynamic Modules for OSGi home page for further information.|
One of the benefits of programming to interfaces is that you are decoupled from the actual implementation; Spring-DM provides a proxy. This has enormous benefits including the ability to dynamically refresh individual bundles without cascading that refresh to unrelated bundles.
To deploy the WAR, copy
You should then see console output similar to the following:
The console output has been reformatted to fit this document.
[2008-05-13 13:26:37.995] fs-watcher <SPSC1000I> Creating web application '/formtags-shared-services-war-1.0.0.RELEASE'. [2008-05-13 13:26:37.998] async-delivery-thread-1 <SPSC1001I> Starting web application '/formtags-shared-services-war-1.0.0.RELEASE'. [2008-05-13 13:26:38.394] fs-watcher <SPDE0010I> Deployment of 'formtags-shared-services-war-1.0.0.RELEASE.war' version '0' completed.Navigating to the appropriate link should render the welcome page.
The final step in the migration is that of a full blown
OSGi application with web support. The SpringSource dm Server introduces a
new packaging and deployment format: the PAR.
A PAR is a standard JAR with a "
file extension which contains all of the modules of your
application (e.g., service, domain, and infrastructure bundles
as well as a WAR or Web Module for web
applications) in a single deployment unit. Moreover, a PAR defines
both a physical and logical application boundary.
For web support above and beyond WAR-based deployment formats, the
SpringSource dm Server introduces a new deployment and packaging option for
OSGi-compliant web applications, the Web Module
format. Web modules have a structure similar to a Shared Services WAR
and therefore build on the support for all three WAR deployment formats.
In addition, web modules benefit from reduced configuration for Spring
MVC based web applications.
The PAR sample is comprised of four directories, as shown below.
formtags-par directory is a Spring-Build project that
understands how to create the PAR from its constituent bundles.
Achieving the appropriate level of granularity for your OSGi application is more of an art than a science. It helps to look at the different requirements:
Table 7.1. Granularity drivers
|Domain/Technical Layering||Applications can be split either by domain (i.e., by use case or vertically) or by their technical layers (i.e., horizontally). Since the Form Tags application essentially has only a single use case, the bundles are split by technical layering (i.e., domain, service, and web).|
|Refreshability||A major benefit of OSGi is that of refreshability: if one bundle is changed, only bundles that have a dependency upon the exported types need to be refreshed. This has a high impact on development time costs as well as production costs. However, this can lead to lots of smaller, fine grained bundles. An example of this granularity would be to separate out the service API and implementation into two different bundles. This means that a change in the implementation wouldn't require any other bundles to be refreshed.|
Ultimately the right level of granularity will depend upon your particular application and team.
|This topic will be revisited in greater detail later in the Programmer Guide in a chapter covering how to build a PAR from scratch.|
The service bundle is identical (except for the
Bundle-SymbolicName) to that
in the shared-services variation of the sample.
The PAR has also separated out the domain classes into their own bundle.
When layering by technical considerations, it is again
somewhat of an unofficial convention to have a
A web module is a SpringSource dm Server construct which is both a web tier artifact and a valid OSGi bundle.
The following image is of the exploded web module JAR
(located inside the distributable
As you can see, at its core, a web module follows the conventions for an OSGi
bundle: the root of the bundle contains the
folder as well as compiled Java classes and class-path resources.
In addition, the web module contains a
folder in the root of the bundle, which serves as the root for the
ServletContext for the deployed web application.
MODULE-INF folder is therefore analogous to the
root of a standard WAR file. Note that there is no
deployment descriptor present in the
folder, since the dm Server will automatically generate an appropriate
web.xml based on web manifest headers.
Because a web module is an OSGi artifact, it follows that information about the
bundle should be in the
In addition, in order to differentiate a web module from any other
type of bundle, you need to specify the
manifest header and set its value to
Without this manifest header, the dm Server's deployment infrastructure
would simply deploy a web module as a standard bundle. The following
/META-INF/MANIFEST.MF for the Form Tags
Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: FormTags Web Module Bundle-SymbolicName: org.springframework.showcase.formtags.web-par Bundle-Vendor: SpringSource Inc. Import-Package: org.springframework.showcase.formtags.domain, org.springframework.showcase.formtags.service Import-Bundle: com.springsource.org.apache.taglibs.standard;version="1.1.2" Import-Library: org.springframework.spring;version="[2.5.4,3.0.0)" Module-Type: Web Web-ContextPath: formtags-par
Contrast this to the original
<?xml version="1.0" encoding="UTF-8"?> <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> <servlet> <servlet-name>formtags</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>formtags</servlet-name> <url-pattern>*.htm</url-pattern> </servlet-mapping> <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> <jsp-config> <taglib> <taglib-uri>http://java.sun.com/jsp/jstl/core</taglib-uri> <taglib-location>/WEB-INF/tld/c.tld</taglib-location> </taglib> <taglib> <taglib-uri>http://java.sun.com/jsp/jstl/fmt</taglib-uri> <taglib-location>/WEB-INF/tld/fmt.tld</taglib-location> </taglib> </jsp-config> </web-app>
The same instructions are specified in the
but they are much more concise. Please read Section 126.96.36.199, “Web Module Manifest Headers”
for detailed information on the requirements of a web module's
and supported manifest headers.
The <jsp-config... fragments are not needed by modern day
Servlet containers, but they are left in the above listing
for consistency with the original
Notice that there are no configuration options in the
to indicate the location of the Spring configuration files. This is because, by default, a single
WebApplicationContext will be created from all the Spring configuration files
/META-INF/spring/*.xml. This shouldn't be surprising as this is normal
behavior for any Spring-DM powered bundle.
Finally we need to construct the PAR itself. The following are the contents of the exploded PAR.
You can see that the PAR itself doesn't contain any resources or Java classes: it simply packages together a related set of bundles as a single, logical unit.
The PAR does however, contain its own
Manifest-Version: 1.0 Application-SymbolicName: org.springframework.showcase.formtags-par Application-Version: 1.0.0 Application-Name: FormTags Showcase Application (PAR)
For more information on the contents of the PAR's
/META-INF/MANIFEST.MF, please consult
Chapter 5, Developing Applications.
You can now deploy the PAR on the dm Server, for example by copying
/dist/formtags-par*.par to the dm Server's
You should then see console output similar to the following:
The console output has been reformatted to fit this document.
[2008-05-13 13:28:57.309] fs-watcher <SPSC1000I> Creating web application '/formtags-par'. [2008-05-13 13:28:57.539] async-delivery-thread-1 <SPSC1001I> Starting web application '/formtags-par'. [2008-05-13 13:28:58.016] fs-watcher <SPDE0010I> Deployment of 'formtags-par' version '1.0.0.RELEASE' completed.
Navigate to http://localhost:8080/formtags-par to see the welcome page.
Note that the web application's context path is explicitly defined via the
The SpringSource dm Server provides out-of-the-box support for deploying standard Java EE WAR files. In addition support for Shared Libraries and Shared Services WAR formats provides a logical migration path away from standard, monolithic WARs toward OSGi-enable Web Modules. The PAR packaging and deployment format enables truly fine grained, loosely coupled, and efficient application development. In general, the migration steps presented in this chapter are fairly straightforward, but developers should set aside time for some up-front design of the bundles themselves.
It is recommended that you take another sample application or indeed your own small application and go through this migration process yourself. This will help you better understand the concepts and principles at work. In addition, it is highly recommended that you familiarize yourself with the Eclipse-based SpringSource dm Server Tools support which is discussed in Chapter 8, Tooling.
SpringSource provides a set of plug-ins for the Eclipse IDE that streamline the development lifecycle of OSGi bundles and PAR applications. The SpringSource dm Server Tools build on top of the Eclipse Web Tools Project (WTP) and Spring IDE, the open-source Spring development tool set.
The SpringSource dm Server Tools support the creation of new OSGi bundle and PAR projects within Eclipse, and the conversion of existing projects into OSGi bundle projects. Projects can then be deployed and debugged on a running dm Server from within Eclipse.
Currently the Tools support Eclipse 3.3 and Eclipse 3.4 with the corresponding version of WTP. Downloading and unzipping the Eclipse IDE for Java EE Developers is the easiest way to start.
Execute the following steps to install the Tools into your Eclipse environment.
Install Spring IDE 2.1.0 from http://springide.org/updatesite/ using the Eclipse Update Manager.
|Don't try to install the "Spring IDE Dependencies (only for Eclipse 3.2.x)" from the "Dependency" category on Eclipse 3.3. This feature is intended only for Eclipse 3.2 and is to keep Spring IDE backward-compatible. You will not be able to continue with the installation if you select this feature on Eclipse 3.3.|
Install the Tools from http://static.springsource.com/projects/sts-dm-server/update/ using the Eclipse Update Manager.
After installing the Tools from the update site outlined in the previous section, you will be able to configure an instance of the dm Server inside Eclipse.
To do so bring up the WTP Servers view (i.e.,→ → → → ). You can now right-click in the view and select " → ". This will bring up a "New Server" dialog. Select "SpringSource dm Server v1.0 Server" in the "SpringSource" category and click " ".
Within the "New Server Wizard" point to the installation directory of the SpringSource dm Server and finish the wizard. After finishing the wizard you should see a SpringSource dm Server entry in the Servers view.
To start, stop, and debug the created SpringSource dm Server instance use the toolbar or the context menu actions of the Servers view.
After successful configuration of an instance of the SpringSource dm Server in Eclipse you can use the Repository Browser to very easily install bundles and libraries from the remote SpringSource Enterprise Bundle Repository.
To open the Repository Browser double-click a SpringSource dm Server instance in the Servers view and select the "Repository" tab in the server editor. Please note that opening of the Editor may take a few seconds as the contents of the local repository needs to be indexed before opening.
The left section of the Repository Browser allows the user to run searches against the SpringSource Enterprise Bundle Repository and displays matching results. The search can take parts of bundle symbolic names, class or package names and allows wildcards such as '?' and '*'. By selecting the checkbox left to a matching bundle and/or library and clicking the "Download" button it is very easy to install new bundles in the SpringSource dm Server. For your convenience JARs containing the bundle source code can be automatically downloaded as well.
Clicking the "Download" button will trigger an Eclipse background job that will download the selected repository artifacts and -- if desired -- the source JARs one after another.
The section on the right displays the currently installed bundles and libraries. Bundles with available sources are visually marked. You can very easily download missing source JARs by using the "Install Sources" button.
The SpringSource dm Server supports different deployment units as discussed earlier in this guide. The Tools define specific project types to support the development of OSGi and PAR projects.
There are two New Project Wizards available within Eclipse that allow for creating new OSGi bundle and PAR projects. The projects created by the wizards are deployable to the integrated dm Server instance without requiring any additional steps.
Those wizards create the required
MANIFEST.MF file and appropriate manifest
To migrate an existing Java Project to be used with the dm Server, the Tools provide a migration action that adds the required meta data to the project. The migration will not change your project's source layout.
Use the context menu action of a project in the Package or Project Explorer and select "→ ".
The Tools provide functionality that makes developing OSGi bundles, especially the editing of MANIFEST.MF files, easier.
While working with OSGi bundles, one of the most interesting and challenging aspects is defining
the package, bundle, and library imports in the manifest and then keeping this in sync
with your compile classpath either in Ant and Maven or Eclipse. In most cases you would typically
be required to manually set up the Eclipse classpath. Ultimately, the Eclipse compile
classpath is still different from the bundle runtime classpath, as normally an entire
JAR file is being made available on the Eclipse classpath but not necessarily at runtime
due to the explicit visibility rules defined in
The Tools address this problem by providing an Eclipse classpath container that
uses an SpringSource dm Server-specific dependency resolution mechanism. This classpath
container makes resolved dependencies available on the project's classpath but allows
only access to those package that are imported explicitly (e.g., via
or implicitly by using
To use the automatic dependency resolution, an OSGi bundle or PAR project needs to be targeted to a configured SpringSource dm Server instance. This can be done from the project's preferences by selecting the runtime on the "Targeted Runtimes" preference page.
|In most scenarios it is sufficient to target the PAR project to a runtime. The nested bundles will then automatically inherit this setting.|
After targeting the project or PAR you will see a "Bundle Dependencies" classpath container in your Java project. It is now safe to remove any manually configured classpath entries.
The classpath container will automatically attach Java source code to the classpath entries by looking for source JARs next to the binary JARs in the SpringSource dm Server's repository. You can also manually override the source code attachment by using the properties dialog on a single JAR entry. This manual attachment will always override the convention-based attachment.
The Tools provide a Bundle Manifest Editor that assists the developer to create and
edit MANIFEST.MF files. The editor understands the SpringSource dm Server specific headers
Import-Bundle and provides content
assist features while editing source code. Furthermore a Eclipse Form-based UI is also
To open the Bundle Manifest Editor right click a MANIFEST.MF file and select "Bundle Manifest Editor" from the "Open With" menu.
|Please note that the SpringSource dm Server specific manifest headers appear in green color to distinguish them from those headers defined in the OSGi specification. This also makes navigating much easier.|
The content assist proposals in the source tab as well as in the UI-based tabs are resolved from the bundle and library repository of an installed and configured SpringSource dm Server. Therefore it is important to target the project or PAR to a specific dm Server instance to indicate to the tooling which bundle repository to use.
|If a OSGi bundle project is not targeted to a instance, either directory or indirectly via a PAR project's targetting, the manifest editor will not be able to provide content assist for importing packages, bundles, and libraries.|
The Dependencies tab of the Bundle Manifest Editor enables the user to easily download and install bundles and libraries from the SpringSource Enterprise Bundle Repository by using the "Download..." buttons next to the "Import Bundle" and "Import Library" sections.
Currently the Tools support direct deployment of WTP Dynamic Web Projects, OSGi bundle and PAR projects to the dm Server from directly within Eclipse.
To deploy an application to the SpringSource dm Server just bring up the context menu on the configured dm Server runtime in the Servers view and choose "Add or Remove Projects...". In the dialog, select the desired project and add it to the list of "Configured projects".
Deploying and undeploying an application from the dm Server certainly works while the SpringSource dm Server is running, but you can also add or remove projects if the dm Server is not running.
Once an application is deployed on the SpringSource dm Server the tooling support will automatically pick up any change to source files -- for example, Java and XML context files -- and refresh the deployed application on the dm Server.
The wait time between a change and the actual refresh can be configured in the configuration editor of the runtime. To bring up that editor, double-click on the configured SpringSource dm Server instance in the Servers view.
Hibernate uses CGLIB to dynamically create subclasses of your entity types at
runtime. To guarantee that Hibernate and CGLIB can correctly see the types,
you must add an
Import-Library for the Hibernate library
into any bundle that uses Hibernate directly and any bundle that contains
types to be persisted by Hibernate.
DataSource implementations use the
class which is incompatible with typical OSGi class loading semantics. To get around this,
DataSource implementation that does not rely on
DriverManager. Versions of the following
DataSources that are known to work in an OSGi environment are available in the
SpringSource Enterprise Bundle Repository.
When using a library that performs bytecode weaving or instrumentation, such as AspectJ,
OpenJPA or EclipseLink, any types that are woven must be able to see the library doing
the weaving. This is accomplished by adding an
Import-Library for the
weaving library into all bundles that are to be woven.
Weaving is often used by JPA implementations to transform persisted types. When using a
JPA provider that uses load-time weaving, an
Import-Library for the
provider is needed in the bundles containing the persisted types.
When using tag libraries within a WAR or Web Module, be sure to include an
Import-Library for the tag library
bundle(s). This will ensure that your module can see the TLD definition and implementing types.
For example, to use the Apache implementation of JSTL, add the following to your bundle's