This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed But Review Recommended These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended. * http://services.gradle.org/distributions/gradle- (404) with 1 occurrences migrated to: https://services.gradle.org/distributions/gradle- ([https](https://services.gradle.org/distributions/gradle-) result 404). ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * http://maven.apache.org/xsd/maven-4.0.0.xsd with 63 occurrences migrated to: https://maven.apache.org/xsd/maven-4.0.0.xsd ([https](https://maven.apache.org/xsd/maven-4.0.0.xsd) result 200). * http://www.apache.org/licenses/LICENSE-2.0 with 4 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200). * http://www.apache.org/licenses/LICENSE-2.0.txt with 64 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0.txt ([https](https://www.apache.org/licenses/LICENSE-2.0.txt) result 200). * http://projects.spring.io/spring-integration with 64 occurrences migrated to: https://projects.spring.io/spring-integration ([https](https://projects.spring.io/spring-integration) result 301). * http://repo.spring.io/libs-milestone with 2 occurrences migrated to: https://repo.spring.io/libs-milestone ([https](https://repo.spring.io/libs-milestone) result 302). * http://repo.spring.io/libs-snapshot with 2 occurrences migrated to: https://repo.spring.io/libs-snapshot ([https](https://repo.spring.io/libs-snapshot) result 302). * http://repo.spring.io/libs-staging-local with 1 occurrences migrated to: https://repo.spring.io/libs-staging-local ([https](https://repo.spring.io/libs-staging-local) result 302). # Ignored These URLs were intentionally ignored. * http://maven.apache.org/POM/4.0.0 with 126 occurrences * http://www.w3.org/2001/XMLSchema-instance with 63 occurrences
Spring Integration - Enricher Sample
Overview
This sample demonstrates how the Enricher components can be used.
Getting Started
You can run the sample application by either
-
running the "Main" class from within STS (Right-click on Main class --> Run As --> Java Application)
-
or from the command line execute:
$ gradlew :enricher:run
This example illustrates the usage of the Content Enricher.
Once the application has started, please execute the various Content Enricher examples by
- entering 1 + Enter
- entering 2 + Enter
- entering 3 + Enter
3 different message flows are triggered. For use-cases 1+2 a User object containing only the username is passed in. For use-case 3 a Map with the username key is passed in and enriched with the User object using the user key:
- 1: In the Enricher, pass the full User object to the request channel.
- 2: In the Enricher, pass only the username to the request channel by using the request-payload-expression attribute.
- 3: In the Enricher, pass only the username to the request channel, executing the same Service Activator as in 2.
Resources
For help please take a look at the Spring Integration documentation: