Welcome to another installment of This Week in Spring! This week I'm in Kansas City, Kansas, hanging out with my pal and Spring Security lead Rob Winch. This week, I'm speaking at the local User Group and the Spring User Group, and I'll be talking to Cerner and a few other large businesses about Spring, Spring Boot and Spring Cloud.

As usual, we've got a lot of great stuff to talk about, so let's go to it!

1. Spring Boot co-lead Phil Webb just announced Spring Boot 1.2.2 and Spring Boot 1.1.11. Both releases are recommended upgrades, and Spring Boot 1.2.2 even includes new support for the Mustache templating library. Nice!
2. Check out John Hann's SpringOne2GX 2014 talk, introducing Rave.js, which brings Spring Boot-concepts to JavaScript
3. I put together a blog on building applications that use the Servlet HTTP session in a scalable manner and in a portable way - from application server, web server, and cloud - with ease.
4. Chris Beams's SpringOne2GX 2014 talk, The Revolution will not be Centralized…

A Framework for all Seasons (and Architectures)

Spring walks an interesting line. It provides a lot of value no matter where you run it, and - because it's built on dependency injection layer - it offers a natural piece of indirection between the underlying layer and the applications that run on top of it. This indirection promotes code portability through decoupling: your application code is ignorant of where the javax.sql.DataSource (or whatever) handle it's using comes from, be it a JNDI lookup, environment variables, or a simple new'd-up bean provided by Spring. This decoupling and the…

We are please to announce the release of Spring Security 4.0.0.RC2.

We were very keen on doing a GA release, but due to community feedback we decided that another RC was necessary. Ultimately, this release resolved nearly 50 tickets.

A summary of changes can be seen below:

• Support for enforcing Same Origin for WebSocket connections
• Refinements in WebSocket Configuration (SEC-2827 SEC-2833 SEC-2853 )
• More intuitive HTTP Response Headers Configuration (SEC-2846)

Assuming everything goes smoothly, the plan is to do a GA release in approximately two weeks. In the meantime, make sure to try…

Welcome to another installment of This Week in Spring! We've got a lot to cover so let's get to it!

1. Our pal Adam Koblentz (from ZeroTurnaround) put up this great post introducing building a websocket application with Spring Boot and JRebel. Check it out!
2. Check out this replay of Mark Fisher, Dr. Mark Pollack, and Sabby Anandan's webinar introducing Spring XD - A Platform for data at scale and developer productivity
3. A huge part of the Pivotal Data Suite, of course, is Spring XD. Last week I surfaced some of the amazing Spring XD wiki content on the new stream processing supports in Spring XD 1.1. Check out the Wiki page for a more detailed look by Spring XD ninja Ilayaperumal Gopinathan.
4. Spring Cloud co-lead Spencer Gibb has been improving the Spring Cloud Netflix integration. Check out this example demonstrating using RxJava's Observable<T> return-values from Spring MVC. Here are the changes…

Speaker: David Syer

Pivotal Spring Security, Spring Boot and Angular JS all have nice features for making it really easy to produce modern applications, so there is potentially a lot of value in making them work together very smoothly. Things to consider are cookies, headers, native clients, various security vulnerabilities and how modern browser technology can help us to avoid them. In this session we show how nice features of the component frameworks can be integrated simply to provide a pleasant and secure user experience. We start with a very basic single-server implementation and scale it up in stages, splitting out backend resources and authentication to separate services. The final state includes a simple API Gateway on the front end implemented declaratively using Spring Cloud, and using this we are able to neatly sidestep a lot of the problems people encounter securing a javascript front end with a distributed back end.

Tuesday, March 10th, 2015 2:00PM GMT (London GMT)Register

Tuesday, March 10th, 2015 10:00AM PDT (San Francisco GMT-07:00) Register

 

Maven's dependency management includes the concept of a bill-of-materials (bom). A bom is a special kind of pom that is used to control the versions of a project's dependencies and provides a central place to define and update those versions.

A number of Spring projects including Spring Framework, Spring Cloud, Spring Boot, and the Spring IO Platform provide boms to make things easier for Maven users. Unfortunately, things haven't been quite so easy if you're using Gradle.

Dependency management in Gradle

Gradle's dependency management uses a ResolutionStrategy to take control of a project's dependency versions. This offers a lot of power and flexibility but doesn't provide a way to reuse the dependency management that's already been declared in a Maven bom. As a result, you have to do so manually. Depending on the bom, this can easily equate to tens of additional lines in your build.gradle…

This tip is drawn heavily from this Wiki-page on Spring XD's streaming support by various Spring XD team-members, and particularly the amazing Ilayaperumal Gopinathan

Spring XD 1.1 is here and is packed with lots of new features. One theme for this release is rich stream processing support. Spring XD 1.1 provides integration with Project Reactor Streams, RxJava Observables, and Spark's streaming.

Let's look specifically at using Reactor, though the concepts are similar across all of the supported streaming APIs.

Messages that are delivered on the Message Bus are accessed from the input Stream. The return value is the output Stream that is the result of applying various operations to the input stream. The content of the output Stream is sent to the message bus for consumption by other processors or sinks. To implement a Stream-based processor module you need to implement the interface org.springframework.xd.reactor.Processor…

Original Author: Enrique Ruiz, Disid

As of STS 3.5.1 Spring Roo support and the Spring Roo runtime are installable from the dashboard rather than being directly included in STS.

With this post we'd like to introduce the Eclipse-based support for Spring Roo so you can take Roo's productivity to STS and you don't even have to leave the development environment! You can build a new application and deploy it to STS in just a few minutes.

We will go step-by-step in order to help you get started quickly:

1.Open your STS IDE.

2. Open STS dashboard.

3. Click on Extensions bottom tab and search Spring Roo.

4. Install Spring Roo (current production release)

5. Install Spring IDE - (Roo extension)

From here on you can just follow the steps of the installation wizard. Along the way you need to review and accept the license agreement and restart STS to finalize the installation.

6. After restarting STS you're ready to work with Spring Roo.

We hope you enjoy this new service. We'll continue to improve the Spring Roo support in future releases of course.

As always we very much value community feedback!

For more project specific information please see the Spring Roo Project Page | or see Spring Roo on GitHub

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!

Welcome to another installment of This Week in Spring! This week I've been in studio recording the next iteration of the Spring Livelessons series, this one on building cloud-native applications (microservices) with Spring Boot, Spring Cloud, and Cloud Foundry. It's been a lot of fun, and - this morning - I took a break to do two 1.5 hour webinars for O'Reilly on building Spring Boot applications and Spring Cloud microservices, both entirely live coded! It's been a fun week for me, and I hope it has for you, as well.

This Thursday the 19th marks the culmination of this year's Lunar New Year, or Chinese new year or Spring festival. What's this to do with Spring (the technology)? Not much, besides being a celebration of better things to come and a great name! So happy new year…