It is my pleasure to announce that the first Spring Framework 3.1 release candidate has - finally - been released this week! We have been working on this release for several months, completing our milestone work and recently adding support for Java SE 7 and for Hibernate 4.0 to the feature list.

Spring Framework 3.1 RC1 completes the 3.1 feature set:

• The environment abstraction and the environment profile mechanism for bean definitions.

• Comprehensive Java-based application configuration based on @Enable* annotations on @Configuration classes.

• An overhaul of the TestContext framework with first-class support for @Configuration classes and for environment profiles.

• Our new "c:" namespace for conveniently specifying constructor arguments by name in a concise inline style.

• The cache abstraction with our declarative caching solution (@Cacheable etc) on top.

• The Servlet 3.0 based WebApplicationInitializer mechanism for bootstrapping a Spring web application without web.xml!

  …

Apache Maven is a very popular choice in the Java community for building and deploying applications.  The Cloud Foundry team has released the Cloud Foundry Maven Plugin to integrate with applications’ development lifecycle, including deployment to the cloud.  The same Maven plugin can be used to manage application pushes and updates to any Cloud Foundry instance.

One of Cloud Foundry’s main promises is to make your life as a developer a whole lot easier without limiting available choices. Cloud Foundry not only supports a plethora of languages (Java, Groovy, Scala, Ruby etc.) and frameworks (Spring, Grails, Rails, Sinatra, Lift etc.) but it also allows you to deploy your applications to different environments. This includes public clouds, such as Cloudfoundry.com and AppFog.com, partner-provided cloud offerings, single VM Micro Cloud Foundry…

Welcome back to another installment of "This Week in Spring." We've got a lot of content this week surrounding Spring Roo, and so, in that spirit, I move that we christen today Rooday, in honor of all the great Roo-related content in this week's roundup.

Things are kicking into over drive at SpringSource as everybody's preparing for SpringOne. This year's show is an exciting one because it'll be the first year where CloudFoundry will be present, which means that there will be lots of content around CloudFoundry and Spring, together, working as an unbeatable combination. I can't wait!

1. InfoQ did an interview with Spring Social lead Craig Walls on the just-released Spring Social 1.0. Fascinating read! Once the interview has whetted your appetite, be sure to try the Spring Social quickstart.

   Spring Social got some great coverage elsewhere, too, including this post from adtmag.com on the new 1.0 release.

 <LI> <a href = "http://www.springsource.org/node/3235">SpringSource Tool Suite 2.7.2 has been released.</a>  The new release features 
	 support for vFabric tc Server 2.6,
	support for Spring Roo 1.2.0.M1, and also updates  Mylyn to 3.6.2. Great stuff!
	
 </li>

<LI>
	<a href = "http://blog.springsource.com/2011/09/14/spring-roo-1-2-0-m1-released/">Spring Roo 1.2.M1 released. 	</a>
	The new release is a <EM>really</EM> exciting one.  There are some exciting <em>backoffice</em…

Java enterprise applications can take many shapes and forms. Depending on their requirements, developers need to decide which specific architectural layers their application needs. Up until now, Spring Roo has taken a pragmatic approach to reduce the often unnecessary complexity introduced by service facade, repository or DAO layers. The newly-released Spring Roo 1.2.0.M1 (see announcement) includes frequently requested support for architectural layers which can be tailored to the needs of the application. This article provides an overview of Roo's new service and repository layer features.

…

The Spring Roo team is delighted to announce the availability of our first 1.2.0 milestone. The Roo 1.2.0.M1 release continues the Roo vision of making it fast and easy to build Spring-based enterprise Java applications. We’ve listened to the community and included in this release some of the most highly-requested features:

• Ten times faster (!). We know many people are using Roo for very large projects, so we’ve continued our attention to Roo internals to ensure it operates smoothly and quickly despite this. Through attention to profiling, file monitoring, disk I/O, XML models and round-tripping, we’ve increased Roo’s performance for large benchmark projects by a factor of 10.
• Now Apache licensed. With Roo 1.0/1.1, we used the GPL license to encourage any improvements made in Roo to be shared with the community. In response to feedback, we’ve shifted to the Apache Software License 2 (ROO-2253) so you have complete flexibility on how you use Roo in commercial and non-commercial projects. This also makes Roo consistent with most of the other Spring projects.
• Moved to GitHub. Social coding is on the rise, and GitHub has become the de facto site for open source source code management. We’re pleased to have moved Roo’s code base to GitHub so that you can easily fork it, make changes, and submit pull requests. This will greatly simplify the receipt of new contributions from the community. Take a look at ROO-2708 or visit https://github.com/SpringSource/spring-roo for more info.
• Repository layer flexibility. It’s now possible to define your own repository layer approach, with full awareness of your choices in the Roo-managed web tiers, integration tests and data-on-demand mechanisms. This is a significant step forward for those preferring a more traditional layering approach than the Roo 1.0/1.1 “Active Record”-like model. Of course the philosophy that favoured the earlier approach remains, so Roo still fully supports embedding convenient Active Record-style methods in entities. You can learn more about this new feature in the Pizza-Shop sample (see the /samples directory of the distribution) and ROO-301.
• Services layers. We also decided to tackle another highly-requested community feature: services layer support. You can now easily add a services layer (via a Roo "service" command) and have this used by the Roo-managed web tiers, integration tests and data-on-demand features. The custom services layers can also be used at the same time as custom repositories, giving you complete flexibility to build whichever application layering you prefer. You can read more in ROO-340 and Stefan Schmidt is publishing a blog shortly giving more details.
• Flexible GWT support.  Now you can skip the UI and just let Roo manage syncing your RequestFactory classes (EntityProxy, RequestContext, and Locator) with your domain model and service layers. Previously the GWT UI scaffolding was mandatory, but with 1.2.0.M1 you can be more selective on how Roo integrates with your project.
• MongoDB support. Whether you’re a Cloud Foundry user, or just a Mongo fan, we’ve now added support for storing your entities in MongoDB. Mongo is a fast, shard-aware, schema-less document database that supports map-reduce and is a good fit for those wanting to use noSQL with Roo. Learn more in ROO-2693.
• Database Reverse Engineering (DBRE) Multi-Schema Support. One of the most popular features in Roo is DBRE support, which allows you to not only scaffold an entity model from your relational schema, but also automatically maintain that entity layer as the schema changes. This takes a schema-first approach to development and we know of users employing DBRE in projects with many hundreds of tables. As part of ROO-1408 we’ve added support for DBRE sourcing its structure from multiple schemas at the same time, and indeed you can even have different schemas manage entities in different Java packages.
• Shell improvements. Lots of people enjoy Roo's usability and indeed the shell has found its way to many other VMware products. We’re pleased that a number of minor fixes have made its way into JLine 1.0 (ROO-2608) and in turn the Roo shell (such as backspace to a previous line will finally work!). You can also run operating system commands directly from the Roo shell via the “!” operator (ROO-2457) and shell on start up now displays the latest community tweets  (ROO-2677).

As you can see, we’ve made a lot of enhancements to Roo 1.2 and look forward to your feedback. We’ve got many exciting new features still coming in the next Roo 1.2 milestone, including JSF/PrimeFaces (ROO-516) support and multi-module Maven (ROO-120) project support. These two are also highly-requested community features.

We hope you enjoy this new release. Please share your experiences via the community forum, follow @SpringRoo for the latest news, or use #springroo in your tweets

Alan Stewart, Project Lead - Spring Roo

Show of hands: Who’s on Facebook? Any Twitter users reading this?

Almost everyone I know is on Facebook, Twitter, LinkedIn, or some other social network site. In fact, most people I know maintain a presence on multiple social network sites. According to recent numbers thrown about, Facebook has over 750 million users and Twitter has over 200 million users. Even my mom is on Facebook.

Okay, you can put your hands down now.

With such a large audience, it can be easy to find business-led motives for building applications that target those users. From a more personal, individual perspective…

Welcome to another edition of "This Week in Spring" There's a lot to get to, so we'll get to it. A quick note: if you're at VMworld 2011 in sunny Las Vegas, come on over to the Cloud Application Platform booth and say hi.

1. What a week for CloudFoundry! The week saw the release and availability of Micro Cloud Foundry, the freely downloadable "PaaS-on-a-stick." Micro Cloud Foundry is a complete, local version of the popular, open source Platform as a Service that lets developers run a full featured cloud on their Mac or PC. Using Micro Cloud Foundry developers can build end-to-end cloud applications locally, without the hassles of configuring middleware while preserving the choice of where to deploy and the ability to scale their applications without changing a line of code.

   To learn more about the Micro Cloud Foundry, check out these three blog posts introducing Micro Cloud Foundry to Spring developers and Grails developers, and introducing the support for Micro CloudFoundry in SpringSource Tool Suite.

   	</li> 
   	
   	<LI>Thomas Risberg blogged today about <A HREF="http://blog.springsource.com/2011/08/30/using-postgres-on-cloud-foundry/">using PostgreSQL on Cloud Foundry</a>. The recently announced  PostgreSQL support   makes CloudFoundry the natural place to deploy your enterprise applications: between MySQL and PostgreSQL there's very likely few speed or feature…

When the new open source Platform-as-a-Service (PaaS) offering Cloud Foundry from VMware launched earlier this year, it included a relational database service powered by MySQL along with the NOSQL options of MongoDB and Redis. One of the promises of the Open PaaS is to provide choice both in languages and frameworks you can develop with and in the database services that are available to use. We now have a new relational database service using PostgreSQL available. This is great since we can now choose between the two most popular open source relational databases. PostgreSQL is is a very…

In my second blog about Grails and Cloud Foundry I introduced a variant of the Grails Twitter example that could be hosted on CloudFoundry.com At the time I mentioned that full text search using the Searchable plugin would limit you to a single application instance because the search indices would be unique to each instance. In other words, you might very easily get different search results depending on which application instance your browser is routed to.

I also said that one option for fixing this problem would be to synchronise the search indices across the instances. But that doesn't sound…