Welcome to another installment of This Week in Spring! As usual, we've got a lot to cover so let's get to it! A lot of this news come from SpringSource itself, from various projects timed to coincide with SpringOne2GX last week. It's like receiving an early birthday gift! And speaking of gifts, if you missed SpringOne2GX, don't worry! We recorded the SpringOne sessions and they will be posted soon. Also, you can check out the show wrap ups for Day 1, Day 2, and Day 3 on SpringSource.org to get a flavor for the conference.

1. Costin Leau announced the release of Spring for Apache Hadoop 1.0.RC1 (the first-ever RC of Spring for Apache Hadoop!) featuring a template, exception translation and declarative runner for Pig and Hive scripts, enhanced map/reduce .jar and tool execution, and refined JVM scripting, M/R, and Cascading runners. Don't miss the upcoming webinar on Nov 8th!

<LI>  Peter Bell did a    <A href = "http://www.infoq.com/presentations/Spring-Data-NoSQL">great presentation on Spring Data and the NoSQL </a>  space for QCon. Be sure to check it out!  </LI> 

2. Yusuf has done a nice job introducing Spring's XA support in terms of the open source Bitronix standalone JTA-XA transaction manager. For an alternative guide, might I humbly suggest this blog post?
3. Oleg Zhurakousky announced the release of Spring Integration 2.1.4 and 2.2.0.RC2 . The new release features pseudo transactions, JPA support, built-in retry support, and a lot more, so be sure to check it out!
4. Costin Leau announced the release of Spring Data Redis 1.0.2, which features cache expiration and ZSet methods, among other things.
5. Thomas Risberg announced the availability of the Spring Data JDBC extensions with Oracle database support, version 1.0.0.RC4.
6. Satish Ab has a nice post on building the web layer with Spring MVC for his sample invoice application.
7. The Mkyong blog has a nice post on how to autowire dependiecnes into custom JSF validators. Very nice post!
8. Our friend Krishna Prasad has a nice post on hwo to implement the control bus pattern with Spring Integration and JMS

Welcome to This Week in Spring, SpringOne2GX 2012 edition! I'm putting this together from day 2 of the SpringOne2GX conference in Washington D.C.!

Last night, we kicked off the event with a great keynote by Juergen Hoeller (pictured above), Dr. Mark Pollack, Graeme Rocher, and Adrian Colyer, some amazing break dancing by international dancer Agame, and a mysterious kangaroo (see below)!

This is the premier event for JVM developers, featuring great speakers from VMWare, SpringSource, TypeSafe, Neo4j, and many others speaking on all manner of topics. The week is just kicking off. While the conference is running, there's also going to be a contest to find the best applications built using SpringSource technologies (Spring, Grails) and deployed to Cloud Foundry. I've seen the prizes (above), and I would enter too if I could!

<P> If you're at the show, be sure to stop by the SpringSource and Cloud Foundry booths in the expo hall and pick up shwag and answers to your lingering questions. I'll be there tomorrow, in the evening.</p><P> Anyway, I won't linger <EM>too</EM> much on what you're missing! Let's move on to this week's roundup because, as usual, there's a lot to cover! </p> 
	
	<OL> 
		<LI>Want to learn about what else has happened at SpringOne2GX? Check <a href= "http://www.springsource.org/node/3704">out this fantastic wrap up of day 1</a></LI>
		<LI> The Spring Data release train has finally arrived…

It's a pleasure to announce that we have just released the GA versions of a variety of Spring Data modules. With this release we continue to manifest the commitment of SpringSource to provide Java developers with tools to work with state-of-the-art persistence technologies. In this blog post I'd like to give you detailed insight into what the release includes, why we decided for a release train and a brief outlook into what the next steps on the Spring Data roadmap are.

The release train

Looking back at the way Spring Data modules were developed, release cycles were usually managed by the individual module leads. Given the different pace and maturity of the modules this caused some issues when trying to work with multiple modules at once. Especially the projects depending on Spring Data Commons were suffering from this problem.

We were working hard on minimizing these issues but eventually came to the conclusion that it makes sense to coordinate the…

The first version of the Scripted code editor has been released this week on github: https://github.com/scripted-editor/scripted.

Although Scripted is a general purpose code editor, the initial focus is building a great JavaScript editing experience. Scripted itself is built entirely in JavaScript and HTML/CSS. It is a browser-based editor that runs locally on a developer's machine with a Node.js instance being used to serve the editor code and perform the editor operations. The only pre-req for running Scripted is that you have a recent version of Node.js installed (we are testing with Node 0.8.11 right now). Scripted reuses the editor component from Eclipse Orion…

Welcome back to another installation of This week in Spring!. There's been a flurry of activity this week at SpringSource as we begin the final leg of the march to SpringOne! We're just a week away, and the show is shaping up every day to be the best show ever! We hope to see you there! Don't miss the day 1 and 2 keynotes from Adrian Colyer, Jurgen Hoeller, Mark Pollack, Graeme Rocher, as well as exciting sessions we've highlighted on SpringSource.org in the last 4 weeks: Going Async - Push Notifications, Client-Side UI Smackdown, Decomposing Applications for Deployability and Scalability, How to build Big Data Pipelines for Hadoop using OSS.

1. Alvin J Rayes put together a nice post on using Spring MVC 3 with Apache Tiles, the templating engine.
2. Tool Suites lead Martin Lippert has announced that Spring Tool Suite and Groovy/Grails Tool Suite 3.1.0 have been released! Nice job, Martin!
3. Spring Security lead Rob Winch has announced that Spring Security 2.0.8, 3.0.8, and 3.1.3 have been released! This brings the total number of outstanding bugs down to 0. Excellent work, Rob!
4. Have you been following the exciting new blogs from the Spring Integration team on the upcoming Spring Integration 2.2 release's new features?

   	 <A href = "http://blog.springsource.org/2012/10/09/spring-integration-2-2-retry-and-more/">Gary Russell has put together a nice blog on the new support for retry in Spring Integration</A>.  The support for retry capabilities originally comes from Spring Batch's support for retrying  
   	 operations, and was then factored out to the <a href="http://www.github.com/springsource/spring-retry">Spring Retry</A> project. Now, you can take advantage of it in Spring Integration flows!
   

5. Gunnar Hillert has a nice post on how to use the new adapters in Spring Integration 2.2 to work with JPA.
6. Learning OAuth? Want to know about the scenarios in which OAuth can help better secure your RESTful APIs? Join Spring ninja Dr. David Syer for his article introducing OAuth, in terms of how Cloud Foundry uses it for the UAA service.

	<LI> Krishna Prasad has put together some very cool posts recently.  I liked his post on connecting systems using…

Introduction

This is the fourth part in a series of blog posts highlighting some of the new features available in Spring Integration 2.2 following the recent release of Release Candidate 1. The first part talks about the MongoDB adapters, the second part talks about transaction synchronization; the third part talks about JPA support.

Spring Integration 2.2 introduces the ability to apply one or more localized AOP Advice elements to a message handler. A number of standard Advice classes has also been provided as well as a sample application that explores the features they provide.

Background

For a general introduction to Aspect Oriented Programming (AOP), see the Spring Documentation

With Spring Integration, to-date, it has been possible to apply an <advice-chain/> to a poller. Assuming Direct channels are being used, an AOP Advice in such a chain applies to the entire flow, encompassing all downstream components. There are times, however, when it would be advantageous to advise just an individual endpoint to, say, retry an…

This is the third part in a series of blog posts highlighting some of the new features available in Spring Integration 2.2 following the recent release of Release Candidate 1. The first part described the new set of MongoDB adapters. In part two we highlighted the new extended support for synchronizing non-transactional resources with transactions.

In this third part today, we would like to introduce the new Java Persistence API (JPA) support that is provided starting with Spring Integration 2.2. The JPA module is persistence-provider-agnostic and has been tested using:

• Hibernate
• OpenJPA
• EclipseLink

As part of the new JPA module, we provide several components for retrieving and persisting JPA entity objects:

• JPA Inbound Channel Adapter
• JPA Outbound Channel Adapter
• JPA Updating Outbound Gateway
• JPA Retrieving Outbound Gateway

Using these components, you can select, create, update and delete entities in your database. Besides persisting data using the entity classes directly, you can also execute queries using the Java Persistence Query Language (JPQL) as well as using native SQL queries. Additionally, named queries are supported as well.

The JPA Sample

In our Spring Integration Samples repository, we provide a sample application demonstrating the JPA support, which we want to use in this blog post to show you how to easily get started.

The provided sample is using an embedded H2 database which contains a single table called PEOPLE. This table is mapped to the Person entity class in package org.springframework.integration.samples.jpa…

It’s JavaOne time again and this year you’ll find sessions on how Spring works with Java SE to address Big Data, NoSQL, and enterprise integration challenges. We’ve always worked hard to ensure that Spring remains at the forefront of enterprise Java by providing timely support for emerging trends and technologies. The numbers suggest that our users appreciate this. A recent report from Evans Data ("Spring Source Usage Study," Evans Data Corporation, September 2011) shows:

• Spring is the framework of choice among expert Java developers. More than two thirds of Java developers are either using Spring today or planning to do so
• Spring usage continues to grow. More than half of existing Spring users expect to grow or significantly grow their use of Spring.
• Spring is delivering results. 70% of Spring users indicate at least a 50% productivity gain by using Spring and 73% indicate at least a 50% time reduction to deliver a completed project.
• Spring users are at the forefront of enterprise Java. Spring users are more cloud ready, and Spring adopters are more likely to have already deployed applications to the cloud.

Spring has always offered deployment flexibility. In the early days this meant a choice of application servers, but now this extends to choice of cloud platforms including our own Cloud Foundry. Spring has always provided strong data access support. In the early days this meant a choice of approaches for accessing a relational database, today this extends to a range of Big Data and NoSQL stores, data processing, and in-memory data grid capabilities. Spring has always valued developer productivity and provided first class support for writing server-side web applications. Today this extends to meet the modern requirements of HATEOAS-based REST APIs.

These are real and pressing concerns within the enterprise today. Cloud is everywhere, and now Big Data is firmly on the enterprise project radar too, creating a range of new requirements:

• Big Data: the need to store and get analytics from gigabytes, terabytes or petabytes of unstructured or semi-structured data
• Fast Data: the increasing need for low latency interactions with large sets of data, often driven by today’s mobile and social apps
• Flexible Data: the need to adapt data access to the most appropriate model for each application
• Cloud Delivery: the growing demand to access data as a service, provisioned on the cloud of your choice.

The latest Harvard Business Review survey indicates that 85% of organizations have Big Data initiatives planned or in progress. Application developers need to deliver capable, high quality solutions that integrate with this new world and can be deployed anywhere, on or off premise. NoSQL and NewSQL are also being used to address a wide range of use cases including:

• Managing large data streams of non-transactional data (logs, clickstreams)
• Fraud detection
• Timelines (a la Twitter)
• Synching offline and online data
• Online gaming
• Document, catalog and content management
• Archiving - storing a large continual stream of data that is still accessible on-line
• Embedded systems (small footprint databases in devices)

See this High Scalability blog entry for more details.

451 Research’s recent survey data highlights the changing shape of the data landscape. One size no longer fits all.

Enterprise developers can start taking advantage of these new technologies today with Spring and the familiar Spring programming model. Spring offers:

• Big Data processing via Spring Data’s support for Apache Hadoop and HBase, as well as Spring Batch and Spring Integration
• In-Memory data grid support via Spring Data GemFire
• Support for NoSQL key-value stores with Spring Data Redis
• Support for NoSQL document stores with Spring Data MongoDB
• Support for NoSQL graph databases with Spring Data Neo4j
• Support for NewSQL databases with SQLFire
• And of course traditional relational databases, such as MySQL, Postgres, Oracle, and DB2, still have their place and can be accessed via Spring JPA and Spring JDBC Extensions, and made accessible via Spring Data REST

The thriving open source community around NoSQL, together with Spring, makes developing for the next generation of data stores and data processing more productive today. We don’t provide a single Java API for all persistence stores; this is not realistic given the fundamental differences between them. But we do provide a common and familiar programming model based on the concepts of templates and, where available, repositories. See Tobias Trelle’s recent InfoQ article for more details.

All in all, JavaOne 2012 is sure to be an action packed week, full of great Java tech talks, keynotes, and sessions including coverage of our own Big Data, NoSQL, and integration initiatives. Developers who want to get hands on with these technologies now also won't want to miss SpringOne 2GX in Washington DC October 15-18, 2012. We have a packed technical agenda covering all aspects of modern enterprise application development.

Introduction

This is the second part in a series of blog posts highlighting some of the new features available in Spring Integration 2.2 following the recent release of Release Candidate 1. The first part talks about the MongoDB adapters.

Spring Integration 2.2 introduces extended support for synchronizing non-transactional resources with transactions.

Background

Spring has provided first class support for synchronizing resources with transactions for many years. In many cases, this facility is used to synchronize transactions managed by multiple transaction managers, in order to implement the 'Best Efforts 1PC' pattern described in Dave Syer's excellent JavaWorld article.

It is often used, for example, to synchronize a JMS commit with a JDBC commit.

Spring Integration has long supported this feature, by defining a <transactional/> element on a poller. This release takes this feature one step further, by allowing synchronization of non-transactional resources with a transaction.

For example, consider a <file:inbound-channel-adapter/> and an Integration application that reads a file when it appears in a directory, and updates a database. This…