Gary Russell
2019-01-17 17:55:57 -05:00
committed by Artem Bilan
parent 462dc98803
commit 48ae91e3d9
4 changed files with 16 additions and 13 deletions

View File

@@ -195,16 +195,17 @@ The following table describes headers that also appear in the `IntegrationMessag
| Header Type
| Usage
| `IntegrationMessageHeaderAccessor.
SEQUENCE_DETAILS`
| `java.util.`
`List<List<Object>>`
| A stack of correlation data used when nested correlation is needed (for example, `splitter->...->splitter->...->aggregator->...->aggregator`).
| IntegrationMessageHeaderAccessor.
SEQUENCE_DETAILS
| java.util.
List<List<Object>>
| A stack of correlation data used when nested correlation is needed (for example,
`splitter->...->splitter->...->aggregator->...->aggregator`).
| `IntegrationMessageHeaderAccessor.
ROUTING_SLIP`
| `java.util.`
`Map<List<Object>, Integer>`
| IntegrationMessageHeaderAccessor.
ROUTING_SLIP
| java.util.
Map<List<Object>, Integer>
| See <<routing-slip>>.
|===

View File

@@ -365,7 +365,7 @@ If this attribute is not provided, the default value is `org.bson.Document`.
* `query` or `query-expression`: Specifies the MongoDB query.
See the http://www.mongodb.org/display/DOCS/Querying[MongoDB documentation] for more query samples.
* `collection-callback`: Reference to an instance of `org.springframework.data.mongodb.core.CollectionCallback`.
Preferable an instance of `org.springframework.integration.mongodb.outbound.MessageCollectionCallback` since 5.0.11 with the request message context.
Preferable an instance of `o.s.i.mongodb.outbound.MessageCollectionCallback` since 5.0.11 with the request message context.
See its Javadocs for more information.
NOTE: You can not have both `collection-callback` and any of the query attributes.

View File

@@ -469,7 +469,7 @@ The preceding configuration works for any `ResettableFileListFilter`.
Starting with version 5.0, the inbound channel adapter can build sub-directories locally, according to the generated local file name.
That can be a remote sub-path as well.
To be able to read a local directory recursively for modification according to the hierarchy support, you can now supply an internal `FileReadingMessageSource` with a new `RecursiveDirectoryScanner` based on the `Files.walk()` algorithm.
See https://docs.spring.io/spring-integration/api/org/springframework/integration/file/remote/synchronizer/AbstractInboundFileSynchronizingMessageSource.html#setScanner-org.springframework.integration.file.DirectoryScanner[`AbstractInboundFileSynchronizingMessageSource.setScanner()]` for more information.
See https://docs.spring.io/spring-integration/api/org/springframework/integration/file/remote/synchronizer/AbstractInboundFileSynchronizingMessageSource.html#setScanner-org.springframework.integration.file.DirectoryScanner[`AbstractInboundFileSynchronizingMessageSource.setScanner()`] for more information.
Also, you can now switch the `AbstractInboundFileSynchronizingMessageSource` to the `WatchService`-based `DirectoryScanner` by using `setUseWatchService()` option.
It is also configured for all the `WatchEventType` instances to react for any modifications in local directory.
The reprocessing sample shown earlier is based on the built-in functionality of the `FileReadingMessageSource.WatchServiceDirectoryScanner`, which uses `ResettableFileListFilter.remove()` when the file is deleted (`StandardWatchEventKinds.ENTRY_DELETE`) from the local directory.

View File

@@ -207,8 +207,10 @@ The following example shows how to use the namespace to configure a file inbound
</int-file:inbound-channel-adapter>
<int:transaction-synchronization-factory id="syncFactory">
<int:after-commit expression="payload.renameTo('/success/' + payload.name)" channel="committedChannel" />
<int:after-rollback expression="payload.renameTo('/failed/' + payload.name)" channel="rolledBackChannel" />
<int:after-commit expression="payload.renameTo(new java.io.File('/success/' + payload.name))"
channel="committedChannel" />
<int:after-rollback expression="payload.renameTo(new java.io.File('/failed/' + payload.name))"
channel="rolledBackChannel" />
</int:transaction-synchronization-factory>
----
====