Since both `hibernate-jpa-2.1-api` and `org.eclipse.persistence.jpa` have similar classes in the same packages ensure that `hibernate-jpa-2.1-api` loads first to meet JPA-2.1 spec requirements in the Hibernate 5.2.5
* 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
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-1898/
There is no guarantee that if `File.exists()`, the real write to file has occurred
* Add `while()` to check not only `File.exists()` but also its `length()` only after that proceed to assert logic
Since we provide a custom `FileNameGenerator` via `fileNameExpression` we should ensure somehow `BeanFactory` injection to that
`FileWritingMessageHandlerSpec` is a `FactoryBean` since version DSL `1.2` and a particular `BPP` takes care about `Spec` internals and register custom `FileNameGenerator` as a bean.
Use standard `FactoryBean` injection in the `lines()` flow to populate the target `FileWritingMessageHandler` to the flow
Generate pom for all project to apply SI Java DSL 1.2 GA
Fixes GH-180 (https://github.com/spring-projects/spring-integration-samples/issues/180)
* Apply `PollerSpec.errorChannel(String)` style
* Replace `fileNameExpression()` to `fileNameGenerator()` to avoid `No BeanFactory` for `EvaluationContext`
* Use `.trigger()` instead of `.handle()` for `FileWritingMessageHandler.trigger()`
* Fix race condition in test, when file exists already, but there is no content yet
JIRA: https://jira.spring.io/browse/INTSAMPLES-149
Polishing - PR Comments
Polishing - Work Around DSL Issue #119
Make test compatible with Windows.
Also reset Application context `DirtiesContext.ClassMode.AFTER_EACH_TEST_METHOD`.
Since tests uses the same target resources we should be sure that they use clear foundation before running
Make `PromiseTest` more fast decreasing `sleep()` in the `MathService`
Kafka-0.10.0 Compatibility
Upgrade to Spring Boot 1.4.0.RELEASE
Regenerate poms according to upgrades
Just fix the test code according Mockito advice:
```
org.mockito.exceptions.misusing.UnfinishedStubbingException:
Unfinished stubbing detected here:
-> at org.springframework.integration.samples.advance.testing.jms.JmsMockTests.verifyJmsMessageOnOutputChannel(JmsMockTests.java:153)
E.g. thenReturn() may be missing.
Examples of correct stubbing:
when(mock.isOk()).thenReturn(true);
when(mock.isOk()).thenThrow(exception);
doThrow(exception).when(mock).someVoidMethod();
Hints:
1. missing thenReturn()
2. you are trying to stub a final method, you naughty developer!
```
JIRA: https://jira.spring.io/browse/INTSAMPLES-148
Upgrade several dependencies, especially OpenJPA-2.4.0 to support Java 8 Class Transformation
Upgrade to DSL-1.1.2 and other polishing
Upgrade to SI-4.3.0.M1
When just importing the ftp example as a maven project, I ran into the issue of a slf4j version discrepancy described here:
http://www.slf4j.org/faq.html#IllegalAccessError
This is solved by adding the specific version dependency of `slf4j-api`.
* Add the specific `slf4j-api` dependency to the Gradle script
* Change the dependency scope for `slf4j-` impl to the `runtime`.
* Regenerate POMs
