Spring Integration Extensions
- 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)
samples directory, you will find samples for the various modules. Please refer to the documentation of each sample for further details.
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.
Related GitHub projects
- Spring Integration
- Spring Integration Samples
- Spring Integration Templates
- [Spring Integration Dsl Groovy]
- [Spring Integration Dsl Scala]
- Spring Integration Pattern Catalog
Report issues via the Spring Integration Extensions JIRA.
Building from source
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+.
Check out the sources
git clone git://github.com/spring-projects/spring-integration-extensions.git
Go into the directory of a specific module
Compile and test, build all jars
Install the modules jars into your local Maven cache
... and discover more commands with
./gradlew tasks. See also the Gradle build and release FAQ.
Import sources into your IDE
Using Eclipse / STS
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:
Once complete, you may then import the projects into Eclipse as usual:
File -> Import -> Existing projects into workspace
Using IntelliJ IDEA
To generate IDEA metadata (.iml and .ipr files), do the following:
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.
Creating Custom Adapters
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.
Staying in touch
Follow the Spring Integration team members and contributors on Twitter:
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!!