Hi Spring fans! In this installment of Spring Tips we'll look at the new API gateway project, Spring Cloud Gateway, to support edge service requirements like rate limiting, circuit breakers, proxying, and more.
Spring Boot provides a lot of autoconfiguration and external binding features, some of which are relevant to Cloud Foundry, and many of which are not. Spring Cloud Connectors is a library that you can use in your application if you want to create your own components programmatically, but it doesn’t do anything “magical” by itself.
Spring Cloud Connectors lays the foundation for connectors that integrate with various Cloud services. It has ships components that allow correct…
Hi Spring fans and welcome to another installation of This Week in Spring! This week I'm in San Francisco and then off to Austin, TX for the epic G3 Summit. If you're around don't hesitate to say hi. Then, it's straight back to San Francisco for next week's premier agile, ops, apps and cloud-centric event worldwide, SpringOne Platform 2017. Do not miss this!
In last week's installment of Spring Tips, I look at testing in Spring-based applications. Check it out!
Spring Framework lead and Spring co-founder Juergen Hoeller just released Spring Framework 5.0.2 and 4.3.13. The new releases are recommended refinements. Of particular note, our Castor XML support has been deprecated, and we're effectively deprecating support for JDK 6.
It is about time: The official end of of commercial JDK 6 support is coming up soon, with Oracle declaring December 2018 and IBM declaring April 2018 as the end of their extended support.
From a Spring perspective, we take the opportunity to deemphasize JDK 6 support on our end. We'll keep tolerating a JDK 6 runtime in the entire Spring Framework 4.3.x line for all further maintenance releases. However, we won't make compromises for JDK 6 anymore, asking you to upgrade to JDK 7+ for fixes that we'd have to work around specifically for JDK 6 on our end.
Hi Spring fans! Welcome to another installment of This Week in Spring! Can you beleive we're less than six weeks away from 2018? Time sure flies when you're having fun!
This week I'm in Los Angeles talking to community members and then taking in the Thanksgiving holiday here in the US surrounded by friends and family. Thanksgiving is a chance to reflect on that for which we are thankful. I am sure that I speak for all of us here on the Spring and Pivotal teams when I say that we are thankful for you. Thank you for making this the most amazing, dynamic, exhilarating and interesting community…
Hi Spring fans! Welcome to another installment of This Week in Spring! This week I am in Casablanca, Morocco for the amazing Devoxx Morocco event talking to developers in the hub of North Africa.
Can you believe it's already the middle of November? And can you believe we are less than a month away from the amazing SpringOne Platform event in San Francisco, CA? I hope you're going!
Now, without further ado, let's get to it.
Spring messaging ninja Oleg Zhurakousky just announced Spring Cloud Stream Elmhurst.M3 / 2.0.0.M3. The new release improves content-type resolution, support for Apache Kafka 0.11+, and introduces a good deal of nice samples.
Spring Data Geode/GemFire lead John Blum just announced Spring Data Geode / GemFire 2.0.0.RC1. The new release updates dependencies, builds on Java 8 (introducing Java 8 types and lambdas), and introduces new samples.
We are pleased to announce the 2.0.0.M3 release of the Spring Cloud Stream Elmhurst release train.
Spring Cloud Stream Elmhurst 2.0.0.M3 is available for use in the Spring Milestone repository. The release notes include relevant information about version compatibility with Spring Boot, Spring Cloud, Spring AMQP, and Spring for Apache Kafka.
The following sections list new features and improvements included in this release:
Improved Content Type Resolution
The content-type resolution has been improved and consolidated in the channel interceptors, which makes it configurable for situations that require application-level customizations. Also, based on the community feedback, we now set the default content-type as application/json. However, it is still possible to override it via BindingProperties or it can be passed with the Message…