dm Server 2.0.0.M4 has been released, and is now available for download.

We've made a lot of progress since 2.0.0.M3, adding a number of new features upon which the users tracking the nightly builds have already given us some excellent feedback. Take a look at the M4 release notes if you're interested in seeing everything that we've been working on. Please keep your feedback coming as comments on our blog, in the forums, and on JIRA.

New and noteworthy

dm Server now embeds Medic: our OSGi serviceability project

• The logging support is now based on LogBack which means that users now have complete control over the format of log output and have the complete range of LogBack's appenders available to them.
• Support for serviceability dumps is now fully extensible. User code running in dm Server can now contribute to serviceability dumps simply by publishing a DumpContributor implementation to the service registry.
• Event log support (the coded messages that are output to the console) is also available to user code. Event log entries can be generated using an EventLogger which can be obtained from the service registry.

We'll be blogging more about Medic, covering how to use it both in dm Server and in plain OSGi, in the coming weeks.

Support for deploying properties files

Admin console enhancements

In addition to the enhancements that…

I'm happy to announce that we just released the final version of SpringSource Tool Suite 2.1.0; the first GA version with major enhancements since making STS freely available.

The release comes with brand-new installers for all supported platforms and bundles latest versions of SpringSource tc and dm Server as well as Spring Roo. Additionally you can choose between distributions based on Eclipse 3.4 and the recently released 3.5 aka Eclipse Galileo.

Because we've seen lots of interest in the new Groovy tools we also offer a bundled download of STS and the Groovy Eclipse Plugin.

Features

The list of new features in STS is long and we already covered some of them in previous blog posts. Review the New & Noteworthy…

SpringSource Tool Suite 2.1.0 is now GA and ready for download. Christian Dupuis' blog post covers all the new features included in the best development tool for building Spring powered applications:

• Eclipse 3.5 (Galileo) support and platform specific installers for Windows/Mac OS X/Linux
• Support for milestones of Spring 3.0 including XML editing and validation, support for @Configuration and @Bean annotations
• Support for milestones of SpringSource dm Server 2.0, RFC66 web modules and SpringSource Bundlor integration
• Integration of Spring Roo for rapid application development
• Optional integration of the new alpha Groovy Eclipse Plugin

        <br>

Dear Spring Community,

We are pleased to announce that Spring .NET 1.3.0 is now available.  

Download | Support | Documentation | Community

This release contains the following new major features:

• Micosoft Test Framework integration - Integration test classes to support MSTest in addition to NUnit.
• TIBCO EMS integration
  • Helper classes to increase your productivity developing messaging

  based applications with TIBCO EMS.

• NVelocity integration - Helper classes to configure a NVelocity template engine in a Spring based application
• VS.NET Solution Templates
  • VS.NET 2008 based solution templates to get you up and running
  …

Update: 15-Aug-09: Comments are now closed.  If you want help installing or to give feedback or ask questions, please join the mailing list ( archive )

For the last couple of months SpringSource has been actively involved in developing the next version of the Eclipse Groovy Tools.  The initial goal has been to evolve them from where they are into a highly optimized environment for the key developer tasks of code development, building and testing. Ideally the experience when working with mixed Groovy/Java projects should feel as good as it does for pure Java projects in Eclipse.

This week the first version of the code has been committed into the codehaus repository and shortly milestone 1 will be released.  An update site (for Eclipse 3.4.2) is available that contains the current development build: http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.4 .  Yes, currently there is no Eclipse 3.5 build of this code yet, but there will be very soon.  (Update! 31-Jul-09 Eclipse 3.5 update site now available at: http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.5…

In April of this year, SpringSource made generally available our first release of tc Server, version 6.0.19.A. The product has been a huge success, in part due to being based on the tried and true Apache Tomcat base which many, many people (and more and more all the time) are using every day. As outlined in an earlier blog post when we introduced 6.0.19.A, we've extended that tried and true core with extensions that make it easier to use and provide key production oriented extensions to Tomcat. And we've surrounded that solid base with the enterprise, production class management and…

Introduction

Spring Integration is a POJO-based light weight, embeddable messaging framework with a loosely coupled programming model aimed to simplify integration of heterogeneous systems based on Enterprise Integration Patterns and without requiring a separate ESB-like engine or proprietary development and deployment environment. On the other hand, OSGi is a paradigm that allows one to compose loosely coupled systems from independent modules called OSGi Bundles. Composing systems from the set of independently developed modules might not be such a new paradigm, we've been doing it (hopefully) for a…

New Features

A set of updates to the SpringSource dm Server Admin Console are available in the nightly builds. This also shows the use of Plans and the RFC66 Web container. There are two new features available, the first lets you look at any service dumps that the dm Server system may have produced and the second lets you explore the state of bundles within OSGi.

A dump may contain many dump items such as stack traces, thread dumps, depending on the initial cause. Dump items are available for viewing in the Admin Console, simply select the dump of interest on the left and then the dump item on the right…

Spring Integration 1.0.3 is now available. You can find links to the download, reference manual, and more at the Spring Integration home. This release includes quite a few changes, but in this blog, I'm going to focus on one in particular. Starting with this version, the samples are fully self-contained and Maven-enabled. That means you can download the distribution, go into the 'samples' directory, run 'mvn install' and then import the projects into a Maven-aware Eclipse instance, such as the SpringSource Tool Suite. Here's the step-by-step breakdown...

Installing and Running the Samples

1. Make sure you have Maven installed and in your path (2.0.9 or later is required). If not, download it and follow the setup instructions: http://maven.apache.org
2. If you don't already have a Maven-aware version of Eclipse, you can download the SpringSource Tool Suite (STS) which will support these projects out-of-the-box (STS even includes support for the OSGi-enabled samples). Alternatively, you can manually add a Maven plugin, such as m2eclipse to an existing Eclipse installation.
3. Download the Spring Integration Samples and unzip.
4. Within the unzipped "samples" directory, run 'mvn install'. You should eventually see output similar to the following:
5. Once STS/Eclipse is up and running, choose 'File -> Import...' and within the Wizard choose 'General -> Existing Projects into Workspace'. Then browse to the unzipped 'samples' directory, and you will see all of the projects selected by default: Either accept all or choose the individual sample(s) that you want to import, and after a few moments of workspace building, you should be ready to run.*

*NOTE: if you import the 'osgi-inbound' project, you will see some errors on that particular project (but you should not see any errors on the other projects after the workspace build completes). Those errors would be resolved after configuring the runtime and the bundle repository. If you would like to work through the OSGi samples, refer to the dedicated chapter in the Reference Manual…