Progress Update

Today I am pleased to announce that we have just released Spring Roo 1.0.0.M1. This release not only features numerous fixes, enhancements and a 31% performance improvement, but also an exciting range of new capabilities including email services, JMS, Spring Web Flow, simplified installation and automatic Selenium support. That's on top of those many capabilities already present in the alpha releases, as mentioned in my earlier blog entry.

In addition to working on the first milestone release, over the last month we've also established the public project infrastructure typical of open source projects. We now have available a community support forum, Jira issue tracking, public Subversion repository, FishEye source monitoring and so on. Some of the comments reported on the #roo Twitter…

Updated: added version control instructions for Git.

For the last few months I've been working with Subbarao Meduri, Graham Charters, Hal Hildebrand and others from the OSGi Enterprise Expert Group on the RFC66 Web Container specification. The Web Container specification defines how WAR files can be deployed on an OSGi service platform in a standard way.

This is extremely interesting for us, because dm Server has supported WAR files for nearly 18 months now and we are excited to be able to work towards a standard model. As an end user, you'll be able to deploy WAR files on OSGi without…

Dear Spring Community,

I'm pleased to announce that the second release candidate of Spring BlazeDS Integration, the open source solution for building Spring-powered RIAs with Adobe Flex, is now available.

Download | Reference Documentation | JavaDocs | Changelog

This is mainly a bug fix release to correct some minor issues found thanks to the fantastic community feedback in response to RC1, but we've also made some key improvements to the way the project is packaged and made available. We are now bundling the comprehensive Spring BlazeDS Integration Test Drive sample application, developed in conjunction with Adobe, together with the project distribution. This version of the Test Drive is set up to be built with Maven, imported into Eclipse, and run with WTP. A short guide to building and running the sample has been added to the reference manual. Additionally, this is the first release to publish Maven-central-compatible POM's, available in our milestone repository.

The community has provided us with excellent feedback throughout the development process, and I encourage anyone interested to get involved by trying out the new functionality and giving us feedback in the community forum and Jira as we push quickly towards a final 1.0.

dm Server 2.0.0.M2 has been released, and is now available for download. In the two sprints since 2.0.0.M1, we've made significant progress towards the final release, both in terms of new features, and in defect fixes. Take a look at the M2 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

Spring 3 support

Improvements to cloning

Watched repositories

Here's some example configuration for a watched repository:

"watched-repo" : {
    "type" : "watched",
    "watchDirectory" : "repository/watched",
    "watchInterval" : 5
}

When managing and transforming as many bundles as are included in the the SpringSource Enterprise Bundle Repository, it becomes very difficult to remember what packages are boot delegated, exported from the system bundle, or from other bundles in your system. This information is important because you probably don't want to import packages that are boot delegated, you probably do want to import system bundle packages at "0", and you want to define custom imports for all others. Remembering which packages are in each of these categories ends up being a bit error prone and defining template…

Today we are pleased to announce the availability of Grails 1.1.1 which whilst providing many incremental improvements over Grails 1.1 also introduces official support for Google AppEngine.

Groovy itself has been running on AppEngine since its launch, but we had to make a few tweaks here and there in Grails to make Grails applications run on AppEngine.

Included in this is the introduction of an AppEngine plugin which replaces Hibernate with JDO (and soon JPA) for persistence in order to take advantage of Google's DataStore API. The AppEngine plugin also integrates the AppEngine development…

Introduction

Recently the M3 milestone of Bundlor has been released (Forum Anouncement). This milestone adds support for Property Substitution and Version Expansion. This blog post explains how to work with these new features to improve the quality of generated Manifests.

Property Substitution

Bundlor can now be used to substitute any property value into your Manifest Template.

Bundle-Name: ${name}
Bundle-Description: Test bundle using new version of Kernel at ${com.springsource.kernel}
Import-Template: com.springsource.kernel.*;version="${com.springsource.kernel}"

This syntax allows you to specify property placeholders for ${name} and ${com.springsource.kernel} and have them substituted at runtime with actual values. The way that these values are passed in is specific to which Bundlor front end is being used.

Specifying Properties at the Command Line

When Bundlor is run from the command line it will use all the properties available as system properties, this does not include any environment variables. The command line script will pass through any variables passed in via -D so the following will provide the ${com.springsource.kernel} property with a value of '2.0.0.RELEASE' and the ${name}…

It was April 27th around 2:39pm, when Rod announced in his SpringOne Europe opening keynote:

Reto Meier, with our partner namics, took a picture as proof of that very moment and published it on flickr.com. Also the audience at SpringOne seemed to be enthusiastic about the announcement and as a consequence the word was spread to outside of the conference soon after.

So here we are, since Rod promised it, we can't get out of it… ;-)

Today we are proud to deliver on Rod's promise and can announce that the first free versions of STS have been published and can be downloaded from the product page…

Dear Spring Community,

I'm pleased to announce that the first release candidate of Spring BlazeDS Integration, the newest of the open source Spring web projects, is now available.

Download | Reference Documentation | JavaDocs | Changelog

In addition to a number of bug fixes and some general refactoring, the main features of note that have been added in this release are:

• Annotation-based configuration of remote destinations
• Numerous customization hooks for things such as exception translation and incorporating third-party adapters
• Full integration with the BlazeDS Message Service, including support for AMF, JMS, and Spring Integration messaging transports

For those upgrading from M2, take note that the <flex:remote-service> tag has been renamed to <flex:remoting-destination> to be more consistent with the BlazeDS nomenclature. Other than that change, the upgrade process from M2 to RC1 should be smooth.

The community has provided us with excellent feedback throughout the development process, and I encourage anyone interested to get involved by trying out the new functionality and giving us feedback in the community forum and Jira as we push quickly towards a full-fledged 1.0.