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.
The Spring Blog
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.
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 monitoring capabilities of the SpringSource management products.
Last week, Mark Fisher introduced you to the new restructured and simplified Spring Integration samples that came out with the new release of Spring Integration 1.0.3 and so far the feedback was very positive.
Beside restructuring and simplifying existing samples we’ve introduced few new samples with the goal of demonstrating some of the benefits of running Spring Integration on OSGi-based platforms.
In this blog using very trivial, yet powerful example we’re going to look at some of the benefits of Spring Integration and OSGi when used together to address dynamic nature of today’s enterprise.
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 and it will be displayed.
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…
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
dm Server now contains the OSGi Web Container reference implementation and uses and builds upon it for all of its web support. As part of this work we’ve also moved to using the standard XML format for the configuration of Tomcat in dm Server.
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 repositories will stay open until they do.
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.
I have a standard war file, named styled.host.war, that contains a very simple index.html page:
<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>
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.