The Spring Integration Extensions project provides extension modules for Spring Integration. This project is part of the SpringSource organization on GitHub.
- Amazon Web Services (AWS) Support
- Hazelcast Support
- Kafka Support
- MQ Telemetry Transport (MQTT) Support
- Print Support
- SMB Support
- SMPP Support
- Splunk Support
- Voldemort Support
- XQuery Support
- Zip Support (Compression and Uncompression)
Under the samples directory, you will find samples for the various modules. Please refer to the documentation of each sample for further details.
Check out the spring-integration tag on Stack Overflow.
These extensions are community-supported projects and, unlike Spring Integation itself, they are not released on a regular schedule. If you have specific requests about an extension, open a GitHub issue for consideration. Contributions are always welcome.
- Spring Integration
- Spring Integration Samples
- Spring Integration Templates
- Spring Integration Dsl Kotlin
- Spring Integration Pattern Catalog
Report issues via the Spring Integration Extensions JIRA.
Each module of the Spring Integration Extensions project is hosted as independent project with its own release cycle. For the build process of individual modules we recommend using a Gradle-based build system modelled after the Spring Integration project. Also, the Spring Integration Adapter Template for SpringSource Tool Suite (STS) provides a Gradle-based build system. For more information, please see How to Create New Components.
Therefore, the following build instructions should generally apply for most, if not all, Spring Integration Extensions. In the instructions below, ./gradlew is invoked from the root of the source tree and serves as a cross-platform, self-contained bootstrap mechanism for the build. The only prerequisites are Git and JDK 1.6+.
git clone git://github.com/spring-projects/spring-integration-extensions.git
cd module-name
./gradlew build
./gradlew install
... and discover more commands with ./gradlew tasks. See also the Gradle build and release FAQ.
When using SpringSource Tool Suite you can directly import Gradle based projects:
File -> Import -> Gradle Project
Just make sure that the Gradle Support for STS is installed. Alternatively, you can also generate the Eclipse metadata (.classpath and .project files) using Gradle:
./gradlew eclipse
Once complete, you may then import the projects into Eclipse as usual:
File -> Import -> Existing projects into workspace
To generate IDEA metadata (.iml and .ipr files), do the following:
./gradlew idea
Pull requests are welcome. Please see the contributor guidelines for details. Additionally, if you are contributing, we recommend following the process for Spring Integration as outlined in the administrator guidelines.
In order to simplify the process of writing custom components for Spring Integration, we provide a Template project for SpringSource Tool Suite (STS) version 3.0.0 and greater. This template is part of the [Spring Integation Templates][] project. For more information please read How to Create New Components.
Follow the Spring Integration team members and contributors on Twitter:
- @m_f_ - Mark Fisher
- @ghillert - Gunnar Hillert
- @z_oleg - Oleg Zhurakousky
- @gprussell - Gary Russell
The Spring Integration Extensions Framework is released under version 2.0 of the Apache License unless noted differently for individual extension Modules, but this should be the rare exception.
We look forward to your contributions!!