5f524dc534
* Fix compatibility after Java DSL migration to the SI Core * Also upgrade all the JMS sample to the JMS 2.0 * Fix default `connectionFactory` bean reference to the current `jmsConnectionFactory` * Remove unsupported JPA-1.0 Spec via `OpenJpaAutoConfiguration`, since the minimum now is JPA-2.0 * Remove non-lambda sample since minimum now is Java 8 * Rename `PromiseTest` to `MonoTest` and fix it to Reactor 3.0 * Fix `stomp-server.xml` to use proper Reactor 3.0 `eactor.util.function.Tuples` for SpEL * Regenerate POMs
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