Based on the Tomcat server that we all know and love, tc Server adds advanced diagnostics, operational management and mission-critical support…

The S2G Forum series is a new conference concept that we are giving a try in Europe: One-day shows in specific regions, with international speakers, and also some regional-language talks thrown into the mix. Munich is the first of those shows this year; further ones are going to follow in Amsterdam on May 11th and in London on May 13th.

The…

Since quite a few users asked for a dependencies distribution (as an alternative to grabbing dependencies via Maven or Ivy), we are providing a third download now: containing an Ivy repository with common third-party jar files. Note that the core framework is separate from the dependencies; the latter are just provided as an additional convenience and do not constitute an inherent part of the framework distribution. You may of course keep using any supported version…

Spring Batch Integration

Part of the 1.0.0.M2 release was the Spring Batch Integration module, recently migrated from Spring Batch and given a new home with Batch Admin. Many of the Batch-Integration cross over use cases are either implemented or demonstrated in Spring Batch…

Spring and Ajax Overview

For the purposes of this article, when I say Ajax, I'm talking about the web browser's ability to communicate with a web server asynchronously using JavaScript. On the server-side, Spring provides the programming model for defining web services, including services consumed by JavaScript clients. On the client-side, nobody rolls their own Ajax framework these days, either. Most use an established JavaScript framework such as jQuery or Dojo…

In this 5 minute screencast you will see how to:

• Develop a simple "contact manager application" using the Roo shell
• Import and edit the project our free IDE, SpringSource Tool Suite (STS)
• Run the Roo-provided integration tests in STS
• Modify the application and understand ITD round-trip support
• Deploy to your IDE's web container
• Use the scaffolded web user interface
• "Push-in refactor" to move source code between Java source files and ITDs
• Remove Roo from the project

Interested? Just click the image below and enjoy...

If you'd like to learn more about Spring Roo, please feel free to visit this link:

• http://www.springsource.org/roo

Quick links:

• Virgo proposal document at Eclipse.org
• Virgo community forum

What does this mean for users of dm Server?

• Project hosting, home pages, forums, and downloads will all be moved to Eclipse.org infrastructure
• The license will change from the current (largely) GPL license, to the Eclipse Public License (EPL)
• It will be much easier for other organizations and community members to get involved in the ongoing development of Virgo

The follow-on release of dm Server will be developed and released from Eclipse.org.

Why is SpringSource making this change?

We set out with a vision to make modular application development a…

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.