Fix Broken Links in Reference
This commit is contained in:
@@ -18,7 +18,7 @@ This guide includes many samples.
|
||||
===== Conversion Service and Converter
|
||||
|
||||
You can now benefit from the conversion service support provided with Spring while configuring many Spring Integration components, such as a https://www.enterpriseintegrationpatterns.com/DatatypeChannel.html[Datatype channel].
|
||||
See <<channel-implementations>> and <<service-activator-introduction>>.
|
||||
See <<channel-implementations>> and <<service-activator>>.
|
||||
Also, the SpEL support mentioned in the previous point also relies upon the conversion service.
|
||||
Therefore, you can register converters once and take advantage of them anywhere you use SpEL expressions.
|
||||
|
||||
|
||||
@@ -194,7 +194,7 @@ For more information see, <<chain>>.
|
||||
|
||||
The `AbstractCorrelatingMessageHandler` provides a new property called `empty-group-min-timeout` to allow empty group expiry to run on a longer schedule than expiring partial groups.
|
||||
Empty groups are not removed from the `MessageStore` until they have not been modified for at least this number of milliseconds.
|
||||
For more information, see <<aggregator-config>>.
|
||||
For more information, see <<aggregator-xml>>.
|
||||
|
||||
[[x3.0-filelistfilter]]
|
||||
===== Persistent File List Filters (file, (S)FTP)
|
||||
|
||||
@@ -214,7 +214,7 @@ For more information, see <<retry-config>>.
|
||||
|
||||
We added the mutually exclusive `group-timeout` and `group-timeout-expression` attributes to `<int:aggregator>` and `<int:resequencer>`.
|
||||
These attributes allow forced completion of a partial `MessageGroup`, provided the `ReleaseStrategy` does not release a group and no further messages arrive within the time specified.
|
||||
For more information, see <<aggregator-config>>.
|
||||
For more information, see <<aggregator-xml>>.
|
||||
|
||||
[[x4.0-redis-metadata]]
|
||||
===== Redis Metadata Store
|
||||
|
||||
@@ -188,7 +188,7 @@ See <<async-gateway>>.
|
||||
===== Aggregator Advice Chain
|
||||
|
||||
`Aggregator` and `Resequencer` now support `<expire-advice-chain/>` and `<expire-transactional/>` child elements to advise the `forceComplete` operation.
|
||||
See <<aggregator-config>> for more information.
|
||||
See <<aggregator-xml>> for more information.
|
||||
|
||||
[[x4.1-script-outbound-channel-adapter]]
|
||||
===== Outbound Channel Adapter and Scripts
|
||||
|
||||
@@ -1467,7 +1467,7 @@ Defaults to `ByteArrayCrLfSerializer`
|
||||
| `true`, `false`
|
||||
| Whether or not connection uses NIO.
|
||||
Refer to the `java.nio` package for more information.
|
||||
See <<note_nio>>.
|
||||
See <<note-nio>>.
|
||||
Default: `false`.
|
||||
|
||||
| `using-direct-buffers`
|
||||
@@ -1484,7 +1484,7 @@ Must be `false` if `using-nio` is `false`.
|
||||
| `true`, `false`
|
||||
| When you use NIO, it may be necessary to resequence messages.
|
||||
When this attribute is set to `true`, `correlationId` and `sequenceNumber` headers are added to received messages.
|
||||
See <<note_nio>>.
|
||||
See <<note-nio>>.
|
||||
Default: `false`.
|
||||
|
||||
| `so-timeout`
|
||||
|
||||
Reference in New Issue
Block a user