https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2256
The `AggregatorDemoTest` fails sporadically with no second part from
reply.
That might be as a result of the cached consumers in the
`CachingConnectionFactory`, so several `<int-jms:inbound-gateway>`
for the topic using the same connectionFactory essentially end up
using the same consumer sequentially.
And Broker considers them as a single consumer, therefore only one
message is sent.
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2239/
Having Hibernate and EclipseLink in the same application isn't a goal.
On the other hand the sample must be concentrate on the Spring Integration,
not a complexity brought by the Spring Boot auto-configuration override.
* Remove the EclipseLink support from the JPA samples and rely only on
the Hibernate auto-configuration
* Remove an appropriate message from the README
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2211
It isn't clear why second message copy is lost, so increase timeout
in case of some fluctuations in the ActiveMQ.
Also increase logging level to DEBUG to see some info in the next failure
The `Jackson2JsonObjectMapper` tries to load any available modules for
the Jackson `ObjectMapper` via `findAndRegisterModules()`.
But if we have a module but don't have a target library, we end up with
the `ClassNotFoundException`.
In our case we fail with the Kotlin because Spring Boot provides
`com.fasterxml.jackson.module:jackson-module-kotlin` dependency and
leaves the rest of required libs for the target application.
* Exclude `com.fasterxml.jackson.module:jackson-module-kotlin`
from all the dependencies.
* Spring Integration `Jackson2JsonObjectMapper` should be revised to use
`Jackson2ObjectMapperBuilder` - https://jira.spring.io/browse/INT-4318
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2059/
Fix `JmsMockTests` stubbing via making endpoint stopped before mocking
Force SI and SF versions via their BOMs imports
Regenerate POMs including `dependencyManagement` for BOMs customization
Fixesspring-projects/spring-integration-samples#198
The `SocketUtils.findAvailableServerSocket()` isn't reliable for port selection and its `socket.close()` may cause a port selection by some other process.
Use OS-selected port for SshdServer in SFTP sample
Revert unexpected refactoring after renaming properties
Upgrade to SSHD-1.4, FTP Server 1.1, fix tests and Boot 2.0 compatibility
Remove `@IntegrationComponentScan` from Boot samples
Since the latest Spring Boot utilize already `@IntegrationComponentScan` for the `@SpringBootApplication` class package, there is no reason to worry about lost `@MessagingGateway`
Reflect Kafka samples changes according latest Spring Boot fixes
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
