Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-2678: fix a couple of typo

Browse Source 
* changes-2.0-2.1.xml: the subject of INT-2678
* delayer.xml <classname> tag typo
This commit is contained in:
Artem Bilan
2012-07-19 11:29:19 +03:00
parent bc63baa3e6
commit 09c92cf04d
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/reference/docbook/changes-2.0-2.1.xml
View File

@@ -314,7 +314,7 @@
<title>New Samples</title> <title>New Samples</title>
<para> <para>
For the 2.1 release of Spring Integration we also expanded the Spring For the 2.1 release of Spring Integration we also expanded the Spring
Integration Samples project and added many new samples, e.g. sampples Integration Samples project and added many new samples, e.g. samples
covering AMQP support, the new payload enricher, a sample illustrating covering AMQP support, the new payload enricher, a sample illustrating
techniques for testing Spring Integration flow fragments, as well as techniques for testing Spring Integration flow fragments, as well as
an example for executing Stored Procedures against Oracle. For details an example for executing Stored Procedures against Oracle. For details

4
src/reference/docbook/delayer.xml
View File

@@ -91,14 +91,14 @@
the ability to not lose Messages on the application shutdown. After application startup, the the ability to not lose Messages on the application shutdown. After application startup, the
<classname>DelayHandler</classname> reads Messages from its Message Group in the <interfacename>MessageStore</interfacename> <classname>DelayHandler</classname> reads Messages from its Message Group in the <interfacename>MessageStore</interfacename>
and reschedules them with a delay based on the original arrival time of the Message (if the delay is numeric). For messages and reschedules them with a delay based on the original arrival time of the Message (if the delay is numeric). For messages
where the delay header was a <className>Date</className>, that is used when rescheduling. where the delay header was a <classname>Date</classname>, that is used when rescheduling.
If a delayed Message remained in the <interfacename>MessageStore</interfacename> more If a delayed Message remained in the <interfacename>MessageStore</interfacename> more
than its 'delay', it will be sent immediately after startup. than its 'delay', it will be sent immediately after startup.
</para> </para>
<para> <para>
The <classname>DelayHandler</classname> can be exported as a JMX <code>MBean</code> The <classname>DelayHandler</classname> can be exported as a JMX <code>MBean</code>
with managed operations <code>getDelayedMessageCount</code> and <code>reschedulePersistedMessages</code>, with managed operations <code>getDelayedMessageCount</code> and <code>reschedulePersistedMessages</code>,
which allows the rescheduling of delayed persisted Messages at runtime, for example, if the which allows the rescheduling of delayed persisted Messages at runtime, for example, if the
<interfacename>TaskScheduler</interfacename> has previously been stopped. These operations can be invoked via a <code>Control Bus</code> command: <interfacename>TaskScheduler</interfacename> has previously been stopped. These operations can be invoked via a <code>Control Bus</code> command:
<programlisting language="java"><![CDATA[ <programlisting language="java"><![CDATA[
Message<String> delayerReschedulingMessage = MessageBuilder.withPayload("@'delayer.handler'.reschedulePersistedMessages()").build(); Message<String> delayerReschedulingMessage = MessageBuilder.withPayload("@'delayer.handler'.reschedulePersistedMessages()").build();