Hot on the heels of Spring 3.0 and Spring DM 1.2.1, I'm delighted to announce that dm Server 2.0 RC1 is now available. RC1 is feature complete and, barring any major problems being found, will be the final 2.0 release early in the new year. So, please download the RC and give us your feedback: it's your last chance to shape the 2.0 release!
If you're interested in what's changed since M6, please take a look at the release notes.
Thank you for all of the feedback that we've had during the development of 2.0. Please keep it coming as we move towards the final release.
There's a lot of great stuff in the 2.0 release. Here's a brief overview:
- dm Shell – we've added a brand new shell in 2.0, that's available both in-process and remotely over ssh. It provides extensive support for managing a dm Server instance and its deployed artifacts.
- Admin console – the admin console has been extensively overhauled in 2.0. It provides, among other things, support for managing and deploying artifacts, examining diagnostic dumps, and examining the bundle wiring both in the live system, and at the time of a resolution failure.
- Plans – dm Server 2.0 introduces support for plans which are powerful alternative to 1.0's PARs for deploying modular applications. A plan can be used to reference all of the artifacts that comprise your application, optionally making the application atomic to tie the child artifact lifecycles together, and scoped to isolate the application from other applications deployed in the same dm Server instance.
- Provisioning – dm Server's always had excellent provisioning support and in 2.0 it's got even better. In addition to the automatic provisioning of bundles based on the needs of the installed applications that was available in 1.0, dm Server 2.0 provides support for provisioning plans, PARs, and configuration from both local and remote repositories.
- Web support – dm Server 2.0 builds upon 1.0's Web support and embeds the Tomcat-based reference implementation for the OSGi Web Container specification, allowing users to deploy vanilla WAR files with all their dependencies in WEB-INF/lib, and Web Application Bundles that import their dependencies via OSGi manifest metadata. The web container is configurable using the standard Tomcat server.xml.
- User region – dm Server 2.0 introduces a user region which isolates the dm Kernel from user-installed applications. Among other things, this simplifies administration as it allows users to focus on user application artifacts and their dependencies without having to deal with those of the kernel as well.
- Spring 3.0 – like many others, we've been tracking the Spring 3.0 milestones and release candidates, and dm Server 2.0 now packages Spring 3.0 final. If you'd prefer to use dm Server 2.0 with a different version of Spring, it can easily be configured to do so.
- Hot deployment – in addition to support for deployment via the admin console, artifacts can also be deployed to dm Server by copying them into the pickup directory, either in archive or exploded form.
- Running as a service – dm Server can now be run as a Windows service or as a Unix background process.
- Logging – as in 1.0, dm Server's logging support is available via SLF4J. In 2.0, the backend has been replaced with LogBack, making it extensively configurable by modifying dm Server's config/serviceability.xml file with a rich set of appenders available out of the box.
- Equinox 3.5 – dm Server 2.0 embeds Equinox 3.5, the reference implementation of OSGi 4.2.