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…

Some of you may have noticed that in recent posts that the dm Server team has been referencing Git repository URLs. The team has been migrating all of its source code and I'm now pleased to announce that this migration is done. The list below contains the Git URLs for the code managed by the dm Server team. If you were referencing the equivalent repositories in SVN, please clone these new repos instead.

This announcement only covers code managed by the dm Server team, and not the entirety of the Spring portfolio. Other projects will be converting at their own pace and the Subversion…

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

In the sprints since 2.0.0.M3, we've made significant progress towards the final release, both in terms of new features, and in defect fixes. Take a look at the M3 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

Integration of the OSGi Web Container reference implementation

Dump analysis in the Admin Console

Using Git as our version control system

Documentation updates

Use of ConfigurationAdmin

Updated application development guide

Working with dm Server's source code

dm Server's Git repositories

Building dm Server from source

Setup

• Java 6 installed and the JAVA_HOME environment variable configured to point to it
• Ant 1.7.1 or later installed
• An ANT_OPTS environment variable configured to provide a max heap of at least 512MB, e.g. ANT_OPTS=Xmx512m
• Git client

With this setup complete you're ready to build dm Server.

Packaging published binaries

The easiest way to build a packaged dm Server zip file is to build one from existing binaries that have already been published:

git clone git://git.springsource.org/dm-server/dm-server.git
cd dm-server
git checkout --track 2.0.0.M3 -b 2.0.0.M3
ant…

Since we announced SpringSource Slices, a number of users and customers have asked about using Slices to make the styling and branding of their Web sites pluggable. In this blog, I'll demonstrate how easy it is with Slices.

Pluggable styling

<html>
	<head>
		<title>SpringSource Slices Pluggable Styling Demonstration</title>
		<link rel="StyleSheet" href="styles/main.css" type="text/css" />
	</head>
	<body>
		<div class="header">
			<div class="title">SpringSource Slices</div>
			<div class="subtitle">Pluggable Styling Demonstration</div>
		</div>
	</body>
</html>

As you can see, it's looking for a CSS file…

I had such a great experience today with Yourkit that I thought I'd write a quick plug. It's been a couple of years since I used it in anger, and even then it was the best tool I could find, but now it really is ultra slick. I haven't done an exhaustive survey of the marketplace, and that wasn't the object of the exercise: I just wanted a tool to solve a problem.

Here's the story of my day; frustration, then irritation, then finally satisfaction. I had a suspected memory leak in Spring Batch and I needed to track it down quickly. The back story to this is I've seen plenty of memory leaks, but I haven't had to deal with one at the coal face for quite some time. I live in STS these days (sometimes dream in it as well), so I needed a tool that worked well in the IDE. I tried two tools, but only because the first choice didn't work. The two I tried were TPTP and Yourkit…

Today marks a big day for Eclipse and for everybody involved with the Eclipse ecosystem: Congratulations to the Eclipse folks for releasing Eclipse 3.5 aka Galileo. You can read more about the release at http://www.eclipse.org/galileo/. I encourage everybody to download Eclipse 3.5 today and try it out.

Since SpringSource is strongly committed to Eclipse and we are building our SpringSource Tool Suite on top of the Eclipse technology stack, I'm excited to report that STS can be installed and used with 3.5. Here are some instructions to get started:

Update: The instructions in this post are outdated and might not work for you. Please refer to the STS Installation Instructions…