Skip to content

Commit b23147b

Browse files
garyrussellartembilan
authored andcommitted
Fix PDF overflows; missing block fences
- Fix most PDF overflows (2 remain) - Add missing block fences to fix ToC/Headings
1 parent 3ff9645 commit b23147b

File tree

12 files changed

+72
-40
lines changed

12 files changed

+72
-40
lines changed

src/reference/asciidoc/endpoint.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -371,6 +371,7 @@ The following example shows how to define an `advice-chain` for a `poller`:
371371
</int:poller>
372372
</int:service-activator>
373373
----
374+
====
374375

375376
For more information on how to implement the `MethodInterceptor` interface, see the https://docs.spring.io/spring/docs/current/spring-framework-reference/core.html#aop-api[AOP sections of the Spring Framework Reference Guide].
376377
An advice chain can also be applied on a poller that does not have any transaction configuration, letting you enhance the behavior of the message flow initiated by the poller.

src/reference/asciidoc/gateway.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -693,7 +693,7 @@ MyCompletableFuture<Invoice> order(Order order);
693693

694694
`CompletableFuture` instances can be used to perform additional manipulation on the reply, as the following example shows:
695695

696-
===
696+
====
697697
[source, java]
698698
----
699699
CompletableFuture<String> process(String data);

src/reference/asciidoc/handler-advice.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -708,6 +708,7 @@ When the entire handler is advised (such as when the handler does not produce re
708708
----
709709
String componentName = ((NamedComponent) target).getComponentName();
710710
----
711+
====
711712

712713
When you implement `MethodInterceptor` directly, you could cast the target object as follows:
713714

@@ -852,7 +853,6 @@ public IntegrationFlow flow() {
852853
...
853854
}
854855
----
855-
====
856856
857857
NOTE: The `IdempotentReceiverInterceptor` is designed only for the `MessageHandler.handleMessage(Message<?>)` method.
858858
Starting with version 4.3.1, it implements `HandleMessageAdvice`, with the `AbstractHandleMessageAdvice` as a base class, for better dissociation.

src/reference/asciidoc/ip.adoc

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1417,13 +1417,15 @@ In that case, it defaults to the default reply timeout (10 seconds).
14171417
| Y
14181418
| Y
14191419
|
1420-
| See `java.net.Socket.setSendBufferSize()`.
1420+
| See `java.net.Socket.`
1421+
`setSendBufferSize()`.
14211422

14221423
| `so-receive-buffer-size`
14231424
| Y
14241425
| Y
14251426
|
1426-
| See `java.net.Socket.setReceiveBufferSize()`.
1427+
| See `java.net.Socket.`
1428+
`setReceiveBufferSize()`.
14271429

14281430
| `so-keep-alive`
14291431
| Y
@@ -1448,7 +1450,8 @@ See `java.net.Socket.setSoLinger()`.
14481450
| Y
14491451
| Y
14501452
|
1451-
| See `java.net.Socket.setTrafficClass()`.
1453+
| See `java.net.Socket.`
1454+
`setTrafficClass()`.
14521455

14531456
| `local-address`
14541457
| N
@@ -1610,7 +1613,7 @@ Default: `true`.
16101613
The following table describes attributes that you can set to configure UDP outbound channel adapters:
16111614

16121615
.UDP Outbound Channel Adapter Attributes
1613-
[cols="1,^1,4", options="header"]
1616+
[cols="2,^1,4", options="header"]
16141617
|===
16151618
| Attribute Name
16161619
| Allowed Values
@@ -1701,7 +1704,7 @@ outgoing UDP packets.
17011704
The following table describes attributes that you can set to configure TCP inbound channel adapters:
17021705

17031706
.TCP Inbound Channel Adapter Attributes
1704-
[cols="1,^1,4", options="header"]
1707+
[cols="2,^1,4", options="header"]
17051708
|===
17061709
| Attribute Name
17071710
| Allowed Values
@@ -1742,7 +1745,7 @@ See "`<<namespace-taskscheduler>>`".
17421745
The following table describes attributes that you can set to configure TCP outbound channel adapters:
17431746

17441747
.TCP Outbound Channel Adapter Attributes
1745-
[cols="1,^1,4", options="header"]
1748+
[cols="2,^1,4", options="header"]
17461749
|===
17471750
| Attribute Name
17481751
| Allowed Values
@@ -1780,7 +1783,7 @@ See "`<<namespace-taskscheduler>>`".
17801783
The following table describes attributes that you can set to configure TCP inbound gateways:
17811784

17821785
.TCP Inbound Gateway Attributes
1783-
[cols="1,^1,4", options="header"]
1786+
[cols="2,^1,4", options="header"]
17841787
|===
17851788
| Attribute Name
17861789
| Allowed Values
@@ -1832,7 +1835,7 @@ The following table describes attributes that you can set to configure TCP outbo
18321835

18331836
[[tcp-ob-gateway-attributes]]
18341837
.TCP Outbound Gateway Attributes
1835-
[cols="1,^1,4", options="header"]
1838+
[cols="2,^1,4", options="header"]
18361839
|===
18371840
| Attribute Name
18381841
| Allowed Values
@@ -1879,7 +1882,7 @@ Only applies if the reply-channel might block (such as a bounded QueueChannel th
18791882

18801883
This module uses the following `MessageHeader` instances:
18811884

1882-
[cols="2,2,4", options="header"]
1885+
[cols="3,3,4", options="header"]
18831886
|===
18841887
| Header Name
18851888
| IpHeaders Constant
@@ -1928,7 +1931,8 @@ When sending to a server-side inbound channel adapter or replying to an inbound
19281931
When using a cached or failover client connection factory, it contains the actual underlying connection ID.
19291932

19301933
| `contentType`
1931-
| `MessageHeaders.CONTENT_TYPE`
1934+
| `MessageHeaders.`
1935+
`CONTENT_TYPE`
19321936
| An optional content type for inbound messages
19331937
Described after this table.
19341938
Note that, unlike the other header constants, this constant is in the `MessageHeaders` class, not the `IpHeaders` class.

src/reference/asciidoc/jdbc.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -953,7 +953,7 @@ The following listing shows the corresponding SQL:
953953
----
954954
CREATE PROCEDURE FIND_ALL_COFFEE_BEVERAGES() \
955955
PARAMETER STYLE JAVA LANGUAGE JAVA MODIFIES SQL DATA DYNAMIC RESULT SETS 1 \
956-
EXTERNAL NAME 'org.springframework.integration.jdbc.storedproc.derby.DerbyStoredProcedures.findAllCoffeeBeverages';
956+
EXTERNAL NAME 'o.s.i.jdbc.storedproc.derby.DerbyStoredProcedures.findAllCoffeeBeverages';
957957
----
958958
====
959959

@@ -1063,7 +1063,7 @@ This `MetadataStore` implementation can be used with adapters such as the follow
10631063
* <<ftp-inbound,FTP inbound channel adapters>>
10641064
* <<sftp-inbound,SFTP inbound channel adapters>>
10651065

1066-
To configure these adapters to use the `JdbcMetadataStore`, declare a Spring bean by using a bean name of `metadataStore`.
1066+
To configure these adapters to use the `JdbcMetadataStore`, declare a Spring bean by using a bean name of `metadataStore`.
10671067
The Feed inbound channel adapter and the feed inbound channel adapter both automatically pick up and use the declared `JdbcMetadataStore`, as the following example shows:
10681068

10691069
====

src/reference/asciidoc/jmx.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -390,12 +390,12 @@ Previously, beans of these types were exported as two distinct MBeans:
390390
+
391391
* The metrics MBean (with an object name such as `intDomain:type=MessageHandler,name=myRouter,bean=endpoint`).
392392
This MBean had metrics attributes and metrics/Lifecycle operations.
393-
* A second MBean (with an object name such as `ctxDomain:name=org.springframework.integration.config.RouterFactoryBean#0,type=MethodInvokingRouter`) was exported with the channel mappings attribute and operations.
393+
* A second MBean (with an object name such as `ctxDomain:name=org.springframework.integration.config.` `RouterFactoryBean#0`,type=MethodInvokingRouter`) was exported with the channel mappings attribute and operations.
394394
+
395395
Now the attributes and operations are consolidated into a single MBean.
396396
The object name depends on the exporter.
397397
If exported by the integration MBean exporter, the object name is, for example: `intDomain:type=MessageHandler,name=myRouter,bean=endpoint`.
398-
If exported by another exporter, the object name is, for example: `ctxDomain:name=org.springframework.integration.config.RouterFactoryBean#0,type=MethodInvokingRouter`.
398+
If exported by another exporter, the object name is, for example: `ctxDomain:name=org.springframework.integration.config.` `RouterFactoryBean#0,type=MethodInvokingRouter`.
399399
There is no difference between these MBeans (aside from the object name), except that the statistics are not enabled (the attributes are `0`) by exporters other than the integration exporter.
400400
You can enable statistics at runtime by using the JMX operations.
401401
When exported by the integration MBean exporter, the initial state can be managed as described earlier.

src/reference/asciidoc/jpa.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -589,6 +589,7 @@ The following example shows how to do so:
589589
public class Student {
590590
591591
...
592+
}
592593
----
593594
====
594595

@@ -989,6 +990,7 @@ public class JpaJavaApplication {
989990

990991
The following example shows all the attributes that you can set on a retrieving outbound gateway and describes the key attributes:
991992

993+
====
992994
[source,xml]
993995
----
994996
<int-jpa:retrieving-outbound-gateway request-channel=""
@@ -1154,7 +1156,7 @@ This section contains various examples of using the updating outbound gateway an
11541156

11551157
In the following example, an updating outbound gateway is persisted by using the `org.springframework.integration.jpa.test.entity.Student` entity class as a JPA defining parameter:
11561158

1157-
===
1159+
====
11581160
[source,xml]
11591161
----
11601162
<int-jpa:updating-outbound-gateway request-channel="entityRequestChannel" <1>

src/reference/asciidoc/mail.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,10 @@ The next section has examples of configuring both types of inbound channel adapt
7070
[IMPORTANT]
7171
====
7272
Normally, when the `IMAPMessage.getContent()` method is called, certain headers as well as the body are rendered (for a simple text email), as the following example shows:
73+
====
7374

7475
====
76+
---
7577
[source]
7678
----
7779
@@ -92,7 +94,6 @@ Starting with version 5.0, messages originating from an IMAP source render the c
9294
If you do not use a header mapper and you wish to revert to the previous behavior of rendering only the body, set the `simpleContent` boolean property on the mail receiver to `true`.
9395
This property now controls the rendering regardless of whether a header mapper is used.
9496
It now allows body-only rendering when a header mapper is provided.
95-
====
9697

9798
[[mail-mapping]]
9899
=== Inbound Mail Message Mapping

src/reference/asciidoc/message.adoc

Lines changed: 43 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -80,18 +80,25 @@ The following table describes the pre-defined message headers:
8080
| An identifier for this message instance.
8181
Changes each time a message is mutated.
8282

83-
| `MessageHeaders.TIMESTAMP`
83+
| `MessageHeaders.
84+
TIMESTAMP`
8485
| java.lang.Long
8586
| The time the message was created.
8687
Changes each time a message is mutated.
8788

88-
| `MessageHeaders.REPLY_CHANNEL`
89-
| `java.lang.Object` (`String` or `MessageChannel`)
89+
| `MessageHeaders.
90+
REPLY_CHANNEL`
91+
| `java.lang.Object`
92+
(`String` or
93+
`MessageChannel`)
9094
| A channel to which a reply (if any) is sent when no explicit output channel is configured and there is no `ROUTING_SLIP` or the `ROUTING_SLIP` is exhausted.
9195
If the value is a `String`, it must represent a bean name or have been generated by a `ChannelRegistry.`
9296

93-
| MessageHeaders.ERROR_CHANNEL
94-
| `java.lang.Object` (`String` or `MessageChannel`)
97+
| MessageHeaders.
98+
ERROR_CHANNEL
99+
| `java.lang.Object`
100+
(`String` or
101+
`MessageChannel`)
95102
| A channel to which errors are sent.
96103
If the value is a `String`, it must represent a bean name or have been generated by a `ChannelRegistry.`
97104
|===
@@ -113,44 +120,56 @@ The following table describes the pre-defined message headers:
113120
| Header Type
114121
| Usage
115122

116-
| `IntegrationMessageHeaderAccessor.CORRELATION_ID`
123+
| `IntegrationMessageHeaderAccessor.
124+
CORRELATION_ID`
117125
| `java.lang.Object`
118126
| Used to correlate two or more messages.
119127

120-
| `IntegrationMessageHeaderAccessor.SEQUENCE_NUMBER`
128+
| `IntegrationMessageHeaderAccessor.
129+
SEQUENCE_NUMBER`
121130
| `java.lang.Integer`
122131
| Usually a sequence number with a group of messages with a `SEQUENCE_SIZE` but can also be used in a `<resequencer/>` to resequence an unbounded group of messages.
123132

124-
| `IntegrationMessageHeaderAccessor.SEQUENCE_SIZE`
133+
| `IntegrationMessageHeaderAccessor.
134+
SEQUENCE_SIZE`
125135
| `java.lang.Integer`
126136
| The number of messages within a group of correlated messages.
127137

128-
| `IntegrationMessageHeaderAccessor.EXPIRATION_DATE`
138+
| `IntegrationMessageHeaderAccessor.
139+
EXPIRATION_DATE`
129140
| `java.lang.Long`
130141
| Indicates when a message is expired.
131142
Not used by the framework directly but can be set with a header enricher and used in a `<filter/>` that is configured with an `UnexpiredMessageSelector`.
132143

133-
| `IntegrationMessageHeaderAccessor.PRIORITY`
144+
| `IntegrationMessageHeaderAccessor.
145+
PRIORITY`
134146
| `java.lang.Integer`
135147
| Message priority -- for example, within a `PriorityChannel`.
136148

137149

138-
| `IntegrationMessageHeaderAccessor.DUPLICATE_MESSAGE`
150+
| `IntegrationMessageHeaderAccessor.
151+
DUPLICATE_MESSAGE`
139152
| `java.lang.Boolean`
140153
| True if a message was detected as a duplicate by an idempotent receiver interceptor.
141154
See "`<<idempotent-receiver>>`".
142155

143-
| `IntegrationMessageHeaderAccessor.CLOSEABLE_RESOURCE`
156+
| `IntegrationMessageHeaderAccessor.
157+
CLOSEABLE_RESOURCE`
144158
| `java.io.Closeable`
145159
| This header is present if the message is associated with a `Closeable` that should be closed when message processing is complete.
146160
An example is the `Session` associated with a streamed file transfer using FTP, SFTP, and so on.
147161

148-
| `IntegrationMessageHeaderAccessor.DELIVERY_ATTEMPT`
149-
| `java.lang.AtomicInteger`
162+
| `IntegrationMessageHeaderAccessor.
163+
DELIVERY_ATTEMPT`
164+
| `java.lang.`
165+
`AtomicInteger`
150166
| If a message-driven channel adapter supports the configuration of a `RetryTemplate`, this header contains the current delivery attempt.
151167

152-
| `IntegrationMessageHeaderAccessor.ACKNOWLEDGMENT_CALLBACK`
153-
| `o.s.i.support.AcknowledgmentCallback`
168+
| `IntegrationMessageHeaderAccessor.
169+
ACKNOWLEDGMENT_CALLBACK`
170+
| `o.s.i.support.`
171+
`Acknowledgment`
172+
`Callback`
154173
| If a message source supports it, a call back to accept, reject, or requeue a message.
155174
See "`<<deferred-acks-message-source>>`".
156175
|===
@@ -176,12 +195,16 @@ The following table describes headers that also appear in the `IntegrationMessag
176195
| Header Type
177196
| Usage
178197

179-
| `IntegrationMessageHeaderAccessor.SEQUENCE_DETAILS`
180-
| `java.util.List<List<Object>>`
198+
| `IntegrationMessageHeaderAccessor.
199+
SEQUENCE_DETAILS`
200+
| `java.util.`
201+
`List<List<Object>>`
181202
| A stack of correlation data used when nested correlation is needed (for example, `splitter->...->splitter->...->aggregator->...->aggregator`).
182203

183-
| `IntegrationMessageHeaderAccessor.ROUTING_SLIP`
184-
| `java.util.Map<List<Object>, Integer>`
204+
| `IntegrationMessageHeaderAccessor.
205+
ROUTING_SLIP`
206+
| `java.util.`
207+
`Map<List<Object>, Integer>`
185208
| See "`<<routing-slip>>`".
186209
|===
187210

src/reference/asciidoc/sftp.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1108,7 +1108,7 @@ You can provide one of these filters by using the `filter` property on the gatew
11081108
See also "`<<sftp-partial>>`".
11091109

11101110
[[sftp-put-command]]
1111-
====Using the `put` Command
1111+
==== Using the `put` Command
11121112

11131113
`put` sends a file to the remote server.
11141114
The payload of the message can be a `java.io.File`, a `byte[]`, or a `String`.

src/reference/asciidoc/stomp.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -195,6 +195,7 @@ To include it in your configuration, provide the following namespace declaration
195195

196196
The following listing shows the available attributes for the STOMP outbound channel adapter:
197197

198+
====
198199
[source,xml]
199200
----
200201
<int-stomp:outbound-channel-adapter

src/reference/asciidoc/xml.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ Assume we have the following XML document (which represents an order of two book
167167
</orderItem>
168168
</order>
169169
----
170-
===
170+
====
171171

172172
This document does not declare a namespace.
173173
Therefore, applying the following XPath Expression works as expected:

0 commit comments

Comments
 (0)