SpringOne2GX 2015 replay: Grails 3.x update

News | Pieter Humphrey | October 19, 2015 | ...

Recorded at SpringOne2GX 2015.

Speakers: Graeme Rocher

Slides: http://www.slideshare.net/SpringCentral/whats-new-in-grails-3

In this talk, Grails project lead Graeme Rocher, will update you on the latest release of Grails and what is coming up during the course of the next year.

Covering all the new features of Grails 3 including the new plugin model, Gradle build and profiles support, this talk promise to be packed full of information for those interested in the latest and greatest from the Grails community.

SpringOne2GX 2015 Replay: Spring Cloud at Netflix

News | Pieter Humphrey | October 19, 2015 | ...

Recorded at SpringOne2GX 2015.

Speakers: Jon Schneider, Taylor Wicksell - Netflix

Web / JavaScript Track

Slides: http://www.slideshare.net/SpringCentral/spring-cloud-at-netflix

Cloud Native Track Spring Cloud Netflix allows you to quickly take your existing Spring Boot application and transform it into a fully cloud-ready service (even if you are operating out of a private data center). This talk will be largely live coded, taking a simple Spring Boot app and progressively augmenting it with more and more production-ready features. 1. Service discovery -- how we have extended Spring Cloud to integrate more seamlessly with Eureka. 2. Real-time Metrics -- Spectator/Atlas integration, including how we fold Spring Boot Actuator metrics into Spectator. We will show you how to use the Atlas stack language to generate real-time metrics graphics. 3. Inter-service Communication/Loading Balancing - When should you choose client-side load balancing (Ribbon) over traditional server-side load balancing? We will explain how Netflix OSS can contain both a client side load balancer in Ribbon and a software router in Zuul and when to use each. 4. Managing Failure - Provide a demo of Hystrix/Spring integration with Turbine. 5. Analytics - How Spring Cloud Netflix makes Spring XD an even more powerful real-time analytics platform with real-time operational insights.

Spring IO Platform 1.1.4 released

Releases | Andy Wilkinson | October 16, 2015 | ...

Spring IO Platform 1.1.4.RELEASE is now available from both repo.spring.io and Maven Central.

This maintenance release upgrades the versions of a number of the projects in the Platform to pick up their latest maintenance releases:

  • Spring Boot 1.2.7.RELEASE
  • Spring Data Evans SR4
  • Spring Framework 4.1.8.RELEASE
  • Spring Integration 4.1.6.RELEASE
  • Spring LDAP 2.0.4.RELEASE
  • Spring Mobile 1.1.5.RELEASE
  • Spring Security 3.2.8.RELEASE
  • Spring Session 1.0.2.RELEASE
  • Spring Social Facebook 2.0.2.RELEASE
  • Spring Social LinkedIn 1.0.2.RELEASE
  • Spring Social Twitter 1.1.2.RELEASE
  • Spring Web Flow 2.4.2.RELEASE
  • Spring Web Services 2.2.2.RELEASE

Spring Boot 1.2.7 available now

Releases | Stéphane Nicoll | October 16, 2015 | ...

Spring Boot 1.2.7 has been released and is available now from repo.spring.io and Maven Central.

This maintenance release includes a number of fixes and most importantly updates the managed Spring Framework dependency to version 4.1.8 (which includes an important security fix). Spring Boot itself also includes a security fix that impacts applications using Undertow.

We recommend an immediate upgrade for all Spring Boot users.

Project Page | GitHub | Issues | Documentation

Spring for Apache Hadoop 2.3 Release Candidate 1 released

Releases | Thomas Risberg | October 15, 2015 | ...

We are pleased to announce the Spring for Apache Hadoop 2.3 RC1 release.

The most important enhancements in this release:

  • Update build to use Spring Framework 4.2.2 [SHDP-509]
  • Update build to use Spring Integration 4.2.0 [SHDP-520]
  • Add FlushTimeoutTrigger to StoreObjectSupport [SHDP-526]
  • Replace internal state machine implementation with new "spring-statemachine" project [SHDP-530]

See the release changelog for details.

We continue to provide version specific artifacts with their respective transitive dependencies in the Spring IO milestone repository:

  • 2.3.0.RC1 (default - Apache Hadoop stable 2.7.1)
  • 2.3.0.RC1-hadoop26 (Apache Hadoop 2.6.0)
  • 2.3.0.RC1-phd30 (Pivotal HD 3.0)
  • 2.3.0.RC1-phd21 (Pivotal HD 2.1)
  • 2.3.0.RC1-cdh5 (Cloudera CDH 5.4)
  • 2.3.0.RC1-hdp23 (Hortonworks HDP 2.3)

Spring Framework 4.2.2, 4.1.8 and 3.2.15 available now

Releases | Stéphane Nicoll | October 15, 2015 | ...

On behalf of the team I am pleased to announce that the Spring Framework 4.2.2, 4.1.8 and 3.2.15 maintenance releases are available now.

Aside from fixing various minor issues across the framework, these releases are designed to prevent Reflected File Download attacks; check the corresponding CVE report for details. We recommend an immediate upgrade for all Spring Framework 3.x and 4.x users.

Spring Framework 4.2.2 also provides WebSocket support for the recently released servers Undertow 1.3 and GlassFish 4.1.1, as well as fine-tuned CORS and JavaScript support. This release serves as the foundation of the upcoming Spring Boot 1.3

The Spring Boot Dashboard in STS - Part 2: Working with Cloud Foundry

Engineering | Martin Lippert | October 15, 2015 | ...

Welcome back Spring community,

In this second part of our blog series about the new Spring Boot Dashboard in the Spring Tool Suite we will move beyond local applications in your workspace and take a look at remote apps deployed to a cloud runtime. If you missed the first part, please take a look it to get familiar with the boot dashboard in STS first.

Cloud runtime support

The initial remote target that we support in the Boot Dashboard is Cloud Foundry. Neither the design nor the implementation of the Boot Dashboard limits this to be the only supported remote target, it is just the first one that we worked on.

The goal for us was to provide a similar experience as for local apps, giving you an easy way to interact, start, stop, update, and lookup log output of your Spring Boot apps on Cloud Foundry. Therefore you can add a Cloud Foundry section to the boot dashboard using the big plus icon in the toolbar.

Once you entered your credentials and selected an org/space, a new section will appear in the boot dashboard, listing the apps that are deployed to this space on Cloud Foundry. You can see the name of the app as well as the number of instances that are configured and that are up and running.

The basic actions work for one or multiple apps on CF in the same or a very similar way to how they work for local apps. You can jump to the console output and it will appear in the console view of STS/Eclipse, you can start and stop apps, you can double-click them to get to a browser window for the running app, you can configure a default path for the app, and you can add/remove tags to/from those apps. You can even execute some of the actions (like start and stop) across targets, if you select multiple entries in the boot dashboard across those target sections.

In addition to the common actions that are suitable for local and apps on Cloud Foundry, there are certain additional actions specifically for apps on Cloud Foundry. The boot dashboard allows you, for example, to delete an app entirely from Cloud Foundry, or to easily jump to the web console.

Deploying to Cloud Foundry

Up to here, we talked about existing apps on Cloud Foundry. But how do you get your apps deployed to Cloud Foundry? There are various ways, using the CLI or the Eclipse Plugin for Cloud Foundry. The boot dashboard offers you another option: you can drag&drop your Spring Boot application directly onto the Cloud Foundry target in the dashboard and it will deploy the Spring Boot app to CF. This is as easy as its sounds.

If your application contains a manifest.yml file, this will be used to configure the application for Cloud Foundry. This typically contains the name of the app, the domain, memory settings, number of instances, and potentially a lot more.

If you don’t have a manifest.yml file in your project, the deploy action will prompt you in a dialog for the basic information it needs to deploy the app.

But take care: if the project contains a manifest.yml file, it will be used to deploy and configure the app. Changes to the configuration on CF that you might have made via the web console will be lost the next time you restart/redeploy/update your app using the boot dashboard. Either configure everything in the manifest.yml file or go without it altogether - at least for the moment. We will be working to improve this to allow more flexible ways of dealing with manifest.yml files and external changes to the config of your app, but that is something to be done in future releases of STS.

Once the app is deployed, the boot dashboard will keep the association between the project in your workspace and the deployed app on Cloud Foundry (and will show this association in the boot dashboard).

Keeping this association between your workspace project and the app on Cloud Foundry makes changes to this app a lot easier. If you change the code in your workspace and press the (re)start button for the app on CF, the boot dashboard will automatically re-push the app (the changes) to Cloud Foundry.

Once you have deployed your apps on Cloud Foundry, you often don’t need to work on everything locally at the same time. Usually you focus on certain parts of the application and sometimes you would like to use use even both: some services running on Cloud Foundry and some services running on your local machine in your IDE. But how do they interact?

Tunneling local services for mixed deployments

As an early experiment, we built a specific feature into the boot dashboard that lets you use all your services and apps on CF and have them call individual services running on your local machine. That way you can focus on individual projects of your landscape and continue to use Cloud Foundry for the rest of your world. You can quickly iterate and work on the code locally - and test it while working with the other parts on Cloud Foundry. Isn’t that great?

They way this works is: You have a service discovery mechanism for your microservices in place. At the moment we support the Eureka service discovery service for this feature. You can start your local Spring Boot app using a special action called “(re)start and expose app via ngrok”. Executing this action will (re)start your local app on your machine. At the same time the action will create a public visible tunnel to this app using the ngrok service. As a result, you get a publicly visible URL that routes all its traffic to your local machine and to the local Spring Boot app that is running on your local machine. The app is automatically configured to register with the remote Eureka using this publicly visible tunnel URL.

Clients to this service will now get this tunnel URL from Eureka instead of (or in addition to) the default instance of your service that might be running on Cloud Foundry already - and will call your locally running service instead of the one on CF. You can iterate on your local service quickly or even debug it.

This mixed deployment scenario is obviously not useful for production or team environments, where multiple people are using the applications on CF simultaneously. But this is extremely useful for testing and development environments.

The support for Cloud Foundry is just a starting point here. The Spring Boot Dashboard is by no means limited or focused on Cloud Foundry. Other remote cloud runtimes could and will be added in the future. One of the next runtimes that we are going to work on is Lattice, but other runtimes are very welcome as well. If you are interested in collaborating on this, let us know. The Spring Boot Dashboard is open-source under the EPL and we would be more than happy to collaborate with you on additional features and adding support for more cloud runtimes to it.


The third part of this series will introduce you to the built-in support for the Spring Boot Devtools and how you can use them from within the Boot Dashboard to make quick modifications to your apps (even on CF) and how to do remote debugging on CF.

Spring on GlassFish 4.1.1 and WildFly 10 / Undertow 1.3

News | Juergen Hoeller | October 14, 2015 | ...

Even if I pointed out that there are no general news in terms of Java EE 7 platform adoption in last week's blog post (since there is still no WebSphere Classic, WebLogic, JBoss EAP or even TomEE with full EE 7 support), the two existing open-source EE 7 platform servers - namely, GlassFish and WildFly - made some fine progress in the meantime:

  • There's a GlassFish 4.1.1 release now, with many sub-project updates - including Tyrus for its WebSocket support.
  • And the WildFly team rushes from major release to major release, arriving at WildFly 10 GA very soon now. The underlying Undertow web server reached 1.3 GA just a few days ago.

Get the Spring newsletter

Thank you!

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

Spring Runtime offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all