Spring Integration 5.0 Milestone 1 Available

Releases | Gary Russell | December 02, 2016 | ...

We are pleased to announce that the first milestone for the 5.0 version of Spring Integration is now available.

This is a new major version, based on Spring Framework 5.0 and requires Java 8; this is the biggest change so far, but the following are also included:

  • The Java DSL is now rolled into the framework itself; there are some minor changes to the DSL, such as the removal of the .handleWithAdapter() methods and some general Factory classes. A complete discussion of the DSL changes can be found in the Migration Guide.

  • Upgrade to Spring Data Kay.

  • Upgrade to Spring AMQP 2.0.

  • First class support for TCP/UDP has been added to the DSL.

  • Spring Integration is now based on Reactor 3.0 and Messaging Gateway Promise methods now have to be changed to return Mono.

  • You can now configure mid-flow transactions via TransactionHandleMessageAdvice for adviceChain Messaging Annotations attribute and <transactional> sub-element when using XML configuration.

Spring Statemachine 1.2.0.RC1 Released

Releases | Janne Valkealahti | December 01, 2016 | ...

We’re pleased to announce a release candicate of Spring Statemachine 1.2.0.RC1. Artifacts are available from Spring Repository.

What we got into this release:

  • Usual bug fixes and small enhancements
  • New api's for tracing and monitoring
  • New monitoring sample
  • Full repository config support for Redis, MongoDB and JPA
  • Boot auto-config enhacements
  • Lot of documentation enhacements

Full changes as usual are available from changelog. We're planning to fire up 1.2.0.RELEASE before xmas and possibly do a second release candicate if any major issues are found.

Thank you for all who have contributed in…

Spring AMQP 2.0 Milestone 1 Available

Releases | Gary Russell | November 30, 2016 | ...

We are pleased to announce the first milestone of Spring AMQP 2.0 is now available.

For a complete list of changes; see the what’s new in the reference manual and the release notes.

Here are some highlights of this release

  • The framework is now fully Java 8 based; several functional interfaces are provided for convenient Lambda implementations (callbacks, ReplyingMessageListener etc). Java 8 is now a requirement. It is also based on Spring Framework 5.0.

  • The framework uses the new 4.0 amqp-client library.

  • A new DirectMessageListenerContainer is now available alongside the existing SimpleMessageListenerContainer. The new container actually has a simpler architecture and the listener is called directly on the amqp-client thread (hence the name Direct…​). See Choosing a Container to help you decide which container is appropriate for your application.

Spring Cloud Brixton.SR7 and Spring Cloud Camden.SR3 Are Available

Releases | Ryan Baxter | November 29, 2016 | ...

On behalf of the team, I am pleased to announce that Brixton Service Release 7 and Camden Service Release 3 of Spring Cloud are available today. The releases can be found in our Spring Release repository and Maven Central.

These releases include primarily bug fixes.

The following modules were updated as part of Brixton.SR7:

The following modules were updated as part of Camden.SR3:

Spring Session 1.3.0 RC1 Released

Releases | Rob Winch | November 23, 2016 | ...

On behalf of the community, I’m pleased to announce the release of Spring Session 1.3.0.RC1. This release release closes lots of community submitted Pull Requests. For a complete list of changes see the changelog.

What’s New in Spring Session 1.3.0 RC1

Highlights include:

Contributions

Without the community we couldn’t be the successful project we are today. I’d like to thank everyone that created issues & provided feedback…

Spring Cloud Data Flow for Apache YARN 1.1.0.RC1 released

Releases | Janne Valkealahti | November 23, 2016 | ...

On behalf of the Spring Cloud Data Flow team, I am pleased to announce the 1.1.0.RC1 release of Spring Cloud Data Flow for Apache YARN.

Spring Cloud Data Flow for Apache YARN allows one to use all the goodness of Spring Cloud Data Flow (like the Shell and UI) while targeting Apache YARN as a backend. Stream components are deployed as individual apps in Apache YARN, leveraging the power of the platform to handle scaling and health monitoring.

This first release candicate

  • Builds upon Spring Cloud Data Flow 1.1.0.RC1 and Spring Cloud Deployer 1.1.0.RC1.
  • Support for keeping multiple deployer versions in hdfs.
  • Preparation of supporting upgrades on Ambari when these become available with Ambari future versions.

First milestone of next-generation Spring Data released

Releases | Oliver Drotbohm | November 23, 2016 | ...

On behalf of the Spring Data team, I’d like to announce the first milestone of the Kay release train. This is a special release train as it's going to ship a new generation of Spring Data that will include a couple of breaking changes going forward.

Infrastructure upgrades

The first and most noticeable change is the upgrade to Java 8 as a minimum baseline (no JDK 6 compatibility anymore) and an upgrade to Spring 5 as framework foundation. In subsequent milestones we're going to ship some significant internal rewrites that will also affect user facing API to make use of the new language…

Spring Cloud Data Flow 1.1 GA released

Releases | Mark Pollack | November 23, 2016 | ...

On behalf of the team, I am pleased to announce the GA release of Spring Cloud Data Flow 1.1. Follow the links in the getting started guide to download the local server implementation and shell to create Stream and Tasks.

General highlights of the 1.1 GA Release include:

  • Builds upon Spring Boot 1.4, Spring Cloud Camden SR2, Spring Integration 4.3 and Spring Cloud Task 1.1 release improvements.

  • Adds LDAP, Basic and File based backend authentication

  • Improvements to OAUTH backed authentication

  • LDAP authentication is now supported with SSL

  • Adds a form-based login page for non-OAUTH backend authentication methods such as the LDAP, Basic and File-based options

  • Adds the ability to pass application specific properties via YAML file. This is particularly useful when deploying streams that require many deployment properties to be set.

  • Portable deployment properties for memory, disk and cpu are in place for support across various runtime implementations.

Spring Cloud Data Flow for Kubernetes 1.1 RC1 released

Releases | Thomas Risberg | November 22, 2016 | ...

On behalf of the team, I am pleased to announce the release of the first release candidate of Spring Cloud Data Flow for Kubernetes 1.1.

Spring Cloud Data Flow for Kubernetes provides support for orchestrating long-running (streaming) and short-lived (task/batch) data microservices on Kubernetes.

The most significant change for this release can be found in the Spring Cloud Deployer for Kubernetes project. Thanks to community contributions from Donovan Muller and Rémon (Ray) Sinnema, we have added support for defining volumes and volume mounts for deployed apps. We support the volume types that have a model supported by the Fabric8 Kubernetes client's kubernetes-model

Spring Cloud Task 1.1.0.RELEASE is now available

Releases | Michael Minella | November 22, 2016 | ...

We are pleased to announce that Spring Cloud Task 1.1.0.RELEASE is now available via Github and the Pivotal download repository. Many thanks to all of those who contributed to this release.

Spring Cloud Task 1.1.0 offers the following features:

This is the generally available release (GA) for 1.1.0. This release addresses key enhancements to the project to allow for better coverage of operational concerns for tasks in a cloud environment. Features new to the 1.1.0 line include:

  • Updated error handling - 1.0.x stored stack traces that were the result of task executions within the TaskExecution#exitMessage field, requiring that this field perform double duty. First it was available for orchestration of tasks (similar to StepExecution#exitStatus in Spring Batch) as well as the storage of stack traces for debugging. In the 1.1.0 release, error messages have been moved to a new field TaskExecution#errorMessage so that each field has it's own, dedicated use.

  • Updated customization options for partitioned batch jobs - In the 1.0.x line for Spring Cloud Task, when launching workers as tasks, there was not a way to customize the command line arguments provided to them. This is an issue in environments like CloudFoundry where you can use command line args to customize configuration without the need to re-push your app. In the new 1.1.0 release, we provide the ability to customize command line arguments via the CommandLineArgsProvider which is similar in functionality to the EnvironmentVariablesProvider introduced in 1.0.2.

Get the Spring newsletter

Stay connected with the Spring newsletter

Subscribe

Get ahead

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

Learn more

Get support

Tanzu Spring 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