spring-dm-server - Kenyth Zeng on Diigo

03 Nov 09

If you want OSGi modular support for your system apps, but don’t want or need to host web applications, then dm Kernel is what you want.

28 Aug 09

dm Server 2.0 M3 | SpringSource Team Blog

blog.springsource.com/...dm-server-20-m3 - Preview

spring-dm-server opensource 2.0 git blog code

27 Apr 09

6.4 Multi bundle integration testing

static.springsource.com/...ch06s04.html - Preview

testing spring-dm-server integration tutorial doc

the use of
classpath*: with respect to the module-context.xml path. This will
cause Spring to look for files that match that path in all of the bundles on the classpath meaning that all
the application beans will be instantiated:
When this test is run, Spring creates an ApplicationContext that is built
from the module-context.xml configuration files from all of the bundles.

6.2 Single bundle integration testing

static.springsource.com/...ch06s02.html - Preview

spring-dm-server doc tutorial testing integration

One of the most common forms of integration testing is ensuring that the object relational mapping in an
application is working properly.

5.4 Trying out the JPA middle tier

static.springsource.com/...ch05s04.html - Preview

spring-dm-server tutorial doc

This can be achieved changing greenpages.app so that it no longer
publishes its Directory implementation.
- how can be achieved to adaptively choose the most appropriate service without modifying configurations or source codes? - on 2009-04-27
Add Sticky Note

5.3 Building the JPA module

static.springsource.com/...ch05s03.html - Preview

spring-dm-server tutorial doc

enable load-time weaving that is required by JPA,
This will result in a bean being created in the application context that is named dataSource.
The bean will be of type javax.sql.DataSource and will be backed by a service found in the
OSGi service registry that implements the javax.sql.DataSource interface.
1 more annotations...
- The Import-Package entries for
  org.springframework.context.weaving and
  org.springframework.transaction.aspectj are needed

26 Apr 09

Martin Lippert: Load-Time Weaving for Spring-DM

martinlippert.blogspot.com/...ime-weaving-for-spring-dm.html - Preview

toread Equinox weaving aspectj blog spring-dm spring-dm-server load-time

I am aware of dm Server also implements ltw for OSGi (not only AspectJ, but for all different kinds of lt weavers), but just for the server, not for spring-dm in general, if I remember this correctly. So if you wish to use spring-dm without a server (client-side, just OSGi, whatever) or with a different one (embedding OSGi in WebSphere, WebLogic, Tomcat, Jetty, whatever) or with a different web support (PAX-Web on top of OSGi) you are now able to use ltw for spring-dm with this bridge to Equinox Aspects.

24 Apr 09

5.5 Working with dependencies

static.springsource.com/...ch05s05.html - Preview

spring-dm-server doc toread

uses a local provisioning repository of bundles and libraries
SERVER_HOME/repository/bundles/usr for bundles, and
SERVER_HOME/repository/libraries/usr for libraries.

5.4 Automatic Imports

static.springsource.com/...ch05s04.html - Preview

spring-dm-server doc

consult the server.profile
file located in the SERVER_HOME/lib directory
which corresponds to the version of the JVM on which the dm Server
is running (e.g., java5-server.profile
or java6-server.profile).

5.3 Programmatic Access to Personality-specific Features

static.springsource.com/...ch05s03.html - Preview

spring-dm-server doc

for a Web Module,
you can use Spring MVC's WebApplicationContextUtils'
getWebApplicationContext(servletContext, attributeName)
method (or other means) to programmatically retrieve a reference to the
WebApplicationContext, which is an instance
of ServerOsgiBundleXmlWebApplicationContext.
For Shared Services WARs, you can programmatically retrieve
the WebApplicationContext directly from the
ServletContext.

5.2 Packaging

static.springsource.com/...ch05s02.html - Preview

format webdev spring-dm-server starred doc OSGi reference

The modules of a PAR have their exported packages imported by the
synthetic context bundle which is used for thread context class loading.
Packaged as an OSGi bundle with a .jar extension
12 more annotations...
- the context configuration files loaded by Spring-DM must contain all web related
  components (e.g., Spring MVC Controllers, Filters, SWF, Spring Security, etc.).
- A web module will not have a root WebApplicationContext
- are not required to contain a web.xml deployment descriptor
- any artifacts which would typically reside in the root of a
  standard WAR are placed in a special directory called MODULE-INF
- root of the
  ServletContext
- this is not
  recommended for web modules
- 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 Import-Package,
  Import-Library, Import-Bundle, etc.
  should be packaged in root of the bundle and added to the Bundle-ClassPath
  accordingly.
- For backwards compatibility with the standard WAR format, third-party libraries
  may be packaged in /MODULE-INF/WEB-INF/lib. Note, however,
  that the use of /MODULE-INF/WEB-INF/lib in a web module is
  strongly discouraged.
- *.htm
- comma-separated list of url-pattern values.
- supports configuration of web modules via web.xml fragments.

4.3 A guide to forming bundles

static.springsource.com/...ch04s03.html - Preview

spring-dm-server modularization doc architecture

4.2 Dependency Types

static.springsource.com/...ch04s02.html - Preview

dependency spring-dm-server OSGi doc

type
dependency and service dependency.

4. Deployment Architecture

static.springsource.com/...ch04.html - Preview

deploy spring-dm-server doc format

passes through a deployment pipeline.
At deployment time, the WAR file is
transformed into an OSGi bundle and installed into Tomcat.
8 more annotations...
- Spring-driven load-time weaving
- 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
  /WEB-INF/lib
- allowing you to declare dependencies on libraries via standard OSGi manifest headers
  such as
  Import-Package
  and
  Require-Bundle
  .
- completely decouple your web-specific deployment
  artifacts from your domain model, service layer, etc.
- new OSGi manifest headers such as Web-DispatcherServletUrlPatterns
  and Web-FilterMappings.
- Based on metadata in your web module's /META-INF/MANIFEST.MF,
  the dm Server will auto-generate an appropriately configured web.xml
  for you on-the-fly
- a PAR can be considered a replacement for an EAR (Enterprise Archive)
- Scoping provides both a
  physical and logical application boundary

3.3 Why the SpringSource dm Server?

static.springsource.com/...ch03s03.html - Preview

doc spring-dm-server

converting
JAR files into bundles and making sure that any libraries needed by those
bundles are also available as OSGi bundles.
Lack of application-level isolation
5 more annotations...
- if you attempt to install two instances of the same
  version of application A (i.e., two sets of bundles B and
  C), a clash will occur, because you cannot deploy multiple bundles with
  the same Bundle-SymbolicName and Bundle-Version combination.
- 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.
- OSGi library concept
- PAR packaging format
- designed from the
  ground up to enable tracing and First Failure Data Capture (FFDC)

23 Apr 09

5.2 Creating the DataSource project

static.springsource.com/...ch05s02.html - Preview

getting-started spring-dm-server tutorial

By default, a bundle project is configured with a Bundle Classpath Container.
Bundlor uses a manifest template to control the contents of the generated manifest.
3 more annotations...
- scan both module-context.xml and osgi-context.xml
- The greenpages.db project needs to be associated with a dm Server instance which has the
  Commons DBCP bundle in its repository.
- There are a few cases where Bundlor will not identify a dependency on a class and, at the moment,
  this is one of them, although this is an area of Bundlor that is being improved all the time.

SpringSource Team Blog » Our plans for building OSGi applications

blog.springsource.com/...for-building-osgi-applications - Preview

plan spring-dm-server feature build-time

generating manifest files automatically from the associated metadata available for an application module.
treating their OSGi manifests as the canonical description of dependency metadata.
10 more annotations...
- uses the manifest as the central dependency descriptor in the IDE and in the offline build. Developers write the OSGi manifest by hand, or with help from tooling, and the manifest is used by the build tooling in a similar way to how Maven uses the pom.xml and Ivy uses ivy.xml.
- developers are carrying out their development tasks as they would for any normal Maven/Eclipse project.
  
  The OSGi manifest file is generated by plugins for Maven and for Eclipse.
- For Ivy 2, the Eclipse plugin support is sadly lacking.
- To support testing is this environment, the plugins will allow for both MANIFEST.MF and TEST.MF files to be written
- Bundlor is a tool that we have been using internally for some time to generate OSGi manifests. We used it predominantly to create all the bundles that you see in our Enterprise Bundle Repository. Bundlor can be used to generate manifests for legacy libraries that were created without much consideration for OSGi. Bundlor can also be used for generating manifests for bundles that you are creating specifially with OSGi in mind. Bundlor removes most of the donkey-work involved in creating high quality bundle manifests.
- the generation process will correctly generate uses metadata for you
- we'll be creating an offline dependency resolver that performs OSGi resolution without starting Equinox or dm Server.
- When you make changes to your code, Bundlor can track what changes have to be made to manifest files and avoid having to recreate all manifests.
- We plan to extend Bundlor to support bulk bundle generation. In this mode, you will be able to save time by pointing Bundlor at a directory of JARs and having Bundlor create bundles for all of them.
- bring dependencies to an higher level introducing the concept of libraries.

4.5 Creating a PAR

static.springsource.com/...ch04s05.html - Preview

getting-started spring-dm-server tutorial

In dm Server, applications consisting of multiple bundles can be packaged as part of a PAR.

4.2 GreenPages set up

static.springsource.com/...ch04s02.html - Preview

getting-started spring-dm-server tutorial

Errors in this configuration may cause the dm Server instance to fail to start later.

21 Apr 09

SpringSource Team Blog » Running Spring Applications on OSGi with the SpringSource Application Platform

blog.springsource.com/...ingsource-application-platform - Preview

spring-dm-server OSGi weaving classloader leak blog load-time discussion

Load-time weaving was one of the most problematic features to support in a robust manner. At the basic level, it requires hooking into the Equinox ClassLoader so that standard ClassFileTransformers can be attached and used during the defineClass calls.
When you start propagating weaving across to other bundles, you really need to know when to stop.
4 more annotations...
- propagating refresh to other bundles that are affected by weaving.
- The Platform fixes this by creating a ClassLoader that imports all the exported packages of every module in your application. This ClassLoader is then exposed as the thread context ClassLoader, enabling third-party libraries to see all the exported types in your application.
- does your auto-importing ClassLoader update dynamically as bundles are registered and deregistered? Have you seen any issues around this? I can imagine a lot of memory leak scenarios with classes being endlessly loaded by this ClassLoader in a long-running server scenario.
- There are certainly some hairy situations with memory leaks. We are in the process of tracking them all down, but I doubt that they will prove to be insurmountable

Kenyth Zeng's Library tagged spring-dm-server → View Popular

dm Kernel | SpringSource Team Blog

dm Server 2.0 M3 | SpringSource Team Blog

6.4 Multi bundle integration testing

6.2 Single bundle integration testing

5.4 Trying out the JPA middle tier

5.3 Building the JPA module

Martin Lippert: Load-Time Weaving for Spring-DM

5.5 Working with dependencies

5.4 Automatic Imports

5.3 Programmatic Access to Personality-specific Features

5.2 Packaging

4.3 A guide to forming bundles

4.2 Dependency Types

4. Deployment Architecture

3.3 Why the SpringSource dm Server?

5.2 Creating the DataSource project

SpringSource Team Blog » Our plans for building OSGi applications

4.5 Creating a PAR

4.2 GreenPages set up

SpringSource Team Blog » Running Spring Applications on OSGi with the SpringSource Application Platform

Selected Tags

Related Tags

Sponsored Links