Files

Spring Operator 4f48dce420 URL Cleanup

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 Success
These URLs were fixed successfully.

* http://www.apache.org/licenses/LICENSE-2.0.txt 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 migrated to:
  https://projects.spring.io/spring-integration ([https](https://projects.spring.io/spring-integration) result 301).
* http://repo.spring.io/libs-milestone migrated to:
  https://repo.spring.io/libs-milestone ([https](https://repo.spring.io/libs-milestone) result 302).
* http://repo.spring.io/libs-snapshot migrated to:
  https://repo.spring.io/libs-snapshot ([https](https://repo.spring.io/libs-snapshot) result 302).
* http://repo.spring.io/libs-staging-local 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
* http://maven.apache.org/xsd/maven-4.0.0.xsd
* http://www.w3.org/2001/XMLSchema-instance

2019-03-06 10:03:19 -05:00

src

INTSAMPLES-150: Switch to Log4j2

2017-09-01 16:14:34 -04:00

pom.xml

URL Cleanup

2019-03-06 10:03:19 -05:00

README.md

INTSAMPLES-131: Fix README.md for Gradle

2014-06-23 10:22:37 -04:00

README.md

Multipart Http Sample

This sample demonstrates how you can send a multipart request to a Spring Integration's HTTP service using 2 scenarios:

Spring's RestTemplate
Spring Integration Http Outbound Gateway

It consists of two parts - Client and Server. There are two client programs:

MultipartRestClient. It uses Spring's RestTemplate to assemble and send multipart request
MultipartClientForHttpOutboundClient. It uses Spring Integration Http Outbound Gateway to send multipart request.

The interesting part about this client is the way it assembles the Multipart request using a plain old Map.

The Server is Spring Integration's HTTP endpoint configuration.

To run this sample:

Deploy project
- If you are using STS and project is imported as Eclipse project in your workspace you can just execute Run on Server
- You can also run gradlew :multipart-http:build and generate the WAR file that you can deploy the conventional way
run the simple test client program: org.springframework.integration.samples.multipart.MultipartClient

You should see the following output from the server:

INFO : ...MultipartClient - Successfully received multipart request: {company=[[Ljava.lang.String;@147e8bd9], company-logo=[org.springframework.integration.http.UploadedMultipartFile@f5e12]}
INFO : ...MultipartClient - company - SpringSource
INFO : org.springframework.integration.samples.multipart.MultipartClient - company-logo - as UploadedMultipartFile: spring09_logo.png