Original author: DISID Corporation

Dear Spring community,

The DISID Spring Roo team is busily working towards the 2.0 release. With Spring Roo 2.0 we would like recover the essence that defines the Roo project:

• Be a rapid application development tool, Roo isn't either a framework nor Maven plugins.
• Intelligent code generation to provide improved productivity.
  • Developers often are forced to spend too much of their time doing things that add too little value, Spring Roo's code generation helps them stay focused.
• Create applications based on the extensive set of Spring technologies: Spring Boot, Spring Data, Spring MVC, Spring Security, etc.
• Generate applications based on best architecture practices like: Service Layer, Repository Layer
• New scaffolding model that generates a fully functional responsive UI based on jQuery and Bootstrap.
• Improve extensibility and increase the collaboration of the Spring Roo project:
  • We will create the “Roo Marketplace”: the alternative to Roobot, easier to maintain and available for everyone, a place to find and keep track on third party addons and Roo Addon Suites.
  • A “Roo Addon Suite” is a great way to package and distribute a set of add-ons together, for example if you want to distribute Roo custom distributions. Roo Addon Suite is based on OSGi R5 Subsystems that provides a really convenient deployment model, without compromising the modularity of Roo.

The new Roo 2.0 is a beginning, in future versions we would like to design a new way to define the view layer components to get a true independence from view layer technologies letting the developers to try the technology that better adjust to their requirements: JSP, Thymeleaf, etc. without losing any benefit.

We have scheduled the work of the relase 2.0 in 3 main milestones:

Milestone 1: Create a smaller and easier to maintain Spring Roo distribution. From 2.0, Roo will contain the runtime and the main addons only, so new versions could be released more frequently and being kept up to date with latest Spring projects:

• Make a better separation between the Spring Roo runtime and the core addons. The Roo runtime APIs (classpath, metadata, support, etc.) must be kept as stable and backwards compatible as possible.
• Move the addons not classified as ”core addon” (GWT, JSF, ...) to their own projects to be maintained by Roo community. If your organization would like to contribute to Roo project by maintaining these addons please contact to: springroo@ disid.com
• Migrate current user guide from docbook to ASCIIdoc.

Milestone 2: Update code generation to use latest Spring technologies

• Update code generation to use the latest Spring framework versions (4.x)
  • Move from Spring framework dependencies to Spring IO Platform
• User Managed POM (ROO-3465, ROO-3478)
• Spring Profiles support
• Annotation based configuration:
  • Move to class configuration in spite of XML configuration
  • Improve application maintanability by using Spring Boot annotations
• Remove Active Record data model in favor of the Repository (Spring Data) based one.
• Generate application arquitecture based on service layer pattern by default

Milestone 3: Move web layer to HTML5

• Responsive UI – View layer based on jQuery, Bootstrap and CSS3

Important: Roo 2.0 might contain API changes and less add-ons than previous version so this release probably won't be backward compatible with 1.3. You can see a more specific roadmap in the SpringRoo JIRA:

As always, you’ll also find Roo on Twitter - either follow @SpringRoo or just include #SpringRoo in your tweets. Stay tuned to Spring Roo news!

Dear Spring community,

We are pleased to announce that the Spring Integration Kafka Support 1.1 GA is now available. Use the Release Repository with Maven or Gradle

compile "org.springframework.integration:spring-integration-kafka:1.1.1.RELEASE"

or download a distribution archive, to give it a spin.

Overview

The main reason of such a quick next point release just after 1.0 GA is to address a number of critical fixes for the upcoming Spring XD 1.1.1 and 1.2 releases. In addition, this release provides performance improvements around message generation streaming scenarios, which required an upgrade to Spring Integration 4.1, which is…

Greetings Spring community,

Spring WS has just released version 2.2.1.RELEASE. This is a patch upgrade with no breaking API or behavior changes. I recommend upgrading to ensure you have the latest fixes. For a listing of completed issues see the report below:

Release Notes | Project Page | GitHub | Issues | Documentation

The artifacts are staged on maven central, http://repo.spring.io/release, and bintray.

Cheers!

I'm pleased to announce the release of Spring Security 4.0.0.RELEASE which closes over 175+ tickets. You can find the highlights below:

WebSocket Support

Spring Security 4 added WebSocket Support. It is now possible to use Spring Security with Spring's WebSocket support.

Spring Data Integration

Spring Security 4 added Spring Data Integration. It is now possible to refer to Spring Security's user within Spring Data queries using SpEL.

Test Support

Spring Security 4 has added Test Support. It is now much easier to write tests with Spring Security applications.

More Secure by Default

As exploits…

The GA release of Spring Data release train Fowler marks the finishing line of 6 month of development. It's time to give you an impression of the content of this release and a brief overview about individual features. The major themes of the Fowler release train were performance improvements and enhanced Java 8 support that are mainly reflected in the Spring Data JPA and MongoDB modules but a lot of other ones have seen significant improvements, too.

The easiest way to upgrade to the Spring Data Fowler release train is by using Spring Boot and configuring the spring-data-releasetrain.version property to Fowler-RELEASE. If you're not using Spring Boot yet, add the Spring Data BOM to your <dependencyManagement />…

I'm pleased to announce the release of Spring Security 3.2.7.RELEASE. This release brings a number of bug fixes including a fix for a regression in the Active Directory support.

Project Site | Reference | Guides | Issues

On behalf of the Spring XD team, I am very pleased to announce the
first maintenance release of Spring XD 1.1.

Download Link: 1.1.1.RELEASE: zip and brew.

The 1.1.1 release includes bug fixes and some enhancements. The full list of tickets is available in our JIRA.

Here are some highlights.

• Improved performance and offset management when using Kafka message bus.
• Support for Spark Streaming's reliable receiver.
• Kryo serialization improvements.
• Option to clean up Rabbit queue/topics when deleting the stream.
• Add a Sqoop example

Feedback is very important, so please get in touch with…

Dear Spring community,

It’s my pleasure to announce that Spring Framework 4.1.6 is available now. This is almost exclusively a bugfix release and therefore a strongly recommended upgrade for all current 4.x users. In particular, we recommend an upgrade from the superseded 4.0.x line as well.

Release Notes | Project Page | GitHub | Issues | Documentation

Spring Framework 4.1.6 is also the first release to be formally compatible with the recently released JDK 8 update 40. Spring 4.1.x supports a wide range of Java runtimes now, from 2010-era JDK 6 variants up until the latest 2015-era JDK…

Recorded at SpringOne2GX 2014. Big Data in Memory

Speaker: John Davies, C24

Big Data Track

Slides: http://www.slideshare.net/SpringCentral/spring-one2gx-2014-john-davies-41130273

OK so everyone’s into big data but they’re usually talking about persistence, disk or more recently SSD, how about memory? We could simply add a few terabytes of RAM but even at $100 per GB that’s going to cost a LOT. What if we could reduce the size of the data by 50 fold and effectively bring the cost RAM down towards cost of disk? Keep Spring Integration, Spring Batch, GemFire in-memory cache, RabbitMQ messaging but reduce your data down to binary, yes bits and bytes rather than objects. Less garbage, less network overhead, same APIs but big-data in memory. John will show a Spring work-flow consuming 7.4kB XML messages, binding them to 25kB Java but storing them in just 450 bytes each, 10 million derivative contracts in-memory on a laptop.

Learn more about Spring XD: http://projects.spring.io/spring-xd

Learn more about Spring Integration: http://projects.spring.io/spring-integration

Learn more about Spring Batch: http://projects.spring.io/spring-batch