aa8dff4cfd
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 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 67 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.txt with 68 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 68 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 1 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 134 occurrences * http://www.w3.org/2001/XMLSchema-instance with 67 occurrences
Advanced Testing Examples
Example test cases that show advanced techniques to test Spring Integration based applications.
For basic testing examples see: basic/testing-examples
Examples
jms.JmsMockTests.java
This test case shows how to test an integration flow that uses JMS inbound channel adapter by using Mockito to mock a JmsTemplate (and dependent JMS objects). The example flow in src/main/resources/integration-config.xml does not depend on JMS but includes some additional error handling on errorChannel. The errorChannel is configured on the JMS adapter. So we want test the entire flow for cases in which an invalid message is received via JMS and routed to errorChannel. How do we do this without requiring a JMS message broker?