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

INT-563 except callouts

Browse Source
This commit is contained in:
Iwein Fuld
2009-03-13 16:34:48 +00:00
parent 229ffc0489
commit 80e9a7b20f
10 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
spring-integration-reference/src/chain.xml
View File

@@ -45,6 +45,7 @@
<service-activator ref="someService" method="someMethod"/>
</chain>]]></programlisting>
</para>
The &lt;header-enricher&gt; used in the above example will set a message header with name "foo" and value "bar" on the message.
</section>
</chapter>

2
spring-integration-reference/src/event.xml
View File

@@ -5,7 +5,7 @@
<para>
Spring Integration also provides support for inbound and outbound <classname>ApplicationEvents</classname>.
To receive events and send to a channel, simply define an instance of Spring Integration's
<classname>ApplicationEventListeningChannelAdapter</classname>. This class in an implementation of Spring's
<classname>ApplicationEventListeningChannelAdapter</classname>. This class is an implementation of Spring's
<interfacename>ApplicationListener</interfacename> interface. By default it will pass all received events as
Spring Integration Messages. To limit based on the type of event, configure the list of event types that you want
to receive with the 'eventTypes' property.

14
spring-integration-reference/src/file.xml
View File

@@ -29,7 +29,7 @@
</para>
<para>
To prevent creating messages for certain files, you may supply a
{@link FileListFilter}. By default, an
<interfacename>FileListFilter</interfacename>. By default, an
<classname>AcceptOnceFileListFilter</classname>
is used. This filter ensures files are picked up only once from the
directory.
@@ -84,15 +84,15 @@
Within this namespace you can reduce the FileReadingMessageSource and wrap
it in an InboundChannelAdapter like this:
<programlisting language="xml"><![CDATA[<file:inbound-channel-adapter id="filesIn"
directory="file:${input.directory.property}"/> (1)
directory="file:${input.directory.property}"/>
<file:inbound-channel-adapter id="filesIn"
directory="file:${input.directory.property}"
filter="customFilterBean" /> (2)
filter="customFilterBean" />
<file:inbound-channel-adapter id="filesIn"
directory="file:${input.directory.property}"
filename-pattern="^test.*$" /> (3)]]></programlisting>
Where (1) is relying on the default filter that just prevents
duplication, (2) is using a custom filter and (3) is using the
filename-pattern="^test.*$" /> ]]></programlisting>
Where the first channel adapter is relying on the default filter that just prevents
duplication. The second is using a custom filter and the third is using the
<emphasis>filename-pattern</emphasis>
attribute to add a
<classname>Pattern</classname>
@@ -168,7 +168,7 @@
<para>
To configure File specific transformers you can use the appropriate
elements from the file namespace.
<programlisting language="xml"><![CDATA[<file-to-bytes-transformer input-channel="intput" output-channel="output" delete-files="true"/>]]></programlisting>
<programlisting language="xml"><![CDATA[<file-to-bytes-transformer input-channel="input" output-channel="output" delete-files="true"/>]]></programlisting>
The
<emphasis>delete-files</emphasis>
option signals the transformer to delete the File after the

8
spring-integration-reference/src/jms.xml
View File

@@ -53,7 +53,7 @@
<integration:poller>
<integration:interval-trigger interval="30" time-unit="SECONDS"/>
</integration:poller>
</jms:inbound-channel-adapter>]]></programlisting>
</jms:inbound-channel-adapter>]]></programlisting>
</para>
</section>
@@ -77,9 +77,9 @@
</para>
<para>
The 'extract-payload' property has the same effect as described above, and once again its default value
is 'true'. Of course, the poller sub-element is not required (not accepted actually) for a message-driven
Channel Adapter. For most usage scenarios, the message-driven approach is better since the Messages will
be passed along to the Spring Integration Message Channel as soon as they are received from the underlying
is 'true'. The poller sub-element is not applicable for a message-driven
Channel Adapter, as it will be actively invoked. For most usage scenarios, the message-driven approach is better since the Messages will
be passed along to the <interfacename>MessageChannel</interfacename> as soon as they are received from the underlying
JMS consumer.
</para>
</section>

2
spring-integration-reference/src/mail.xml
View File

@@ -100,7 +100,7 @@
<para>
When using the namespace support, a <emphasis>header-enricher</emphasis> Message Transformer is also available.
This simplifies the application of the headers mentioned above to any Message prior to sending to the
Mail-sending Channel Adapter. Also, note that a boolean value c
Mail-sending Channel Adapter.
<programlisting language="xml"><![CDATA[<mail:header-enricher subject="Example Mail"
to="to@example.org"
cc="cc@example.org"

40
spring-integration-reference/src/resequencer.xml
View File

@@ -39,63 +39,63 @@
&lt;channel id="outputChannel"/&gt;
&lt;resequencer id="completelyDefinedResequencer" <co id="resxml1" />
input-channel="inputChannel" <co id="resxml2" />
output-channel="outputChannel" <co id="resxml3" />
discard-channel="discardChannel" <co id="resxml4" />
release-partial-sequences="true" <co id="resxml5" />
timeout="42" <co id="resxml6" />
send-partial-result-on-timeout="true" <co id="resxml7" />
reaper-interval="135" <co id="resxml8" />
tracked-correlation-id-capacity="99" <co id="resxml9" />
send-timeout="86420000" <co id="resxml10" /> /&gt; </programlisting>
&lt;resequencer id="completelyDefinedResequencer" <co id="resxml1-co" linkends="resxml1" />
input-channel="inputChannel" <co id="resxml2-co" linkends="resxml2"/>
output-channel="outputChannel" <co id="resxml3-co" linkends="resxml3"/>
discard-channel="discardChannel" <co id="resxml4-co" linkends="resxml4"/>
release-partial-sequences="true" <co id="resxml5-co" linkends="resxml5"/>
timeout="42" <co id="resxml6-co" linkends="resxml6"/>
send-partial-result-on-timeout="true" <co id="resxml7-co" linkends="resxml7"/>
reaper-interval="135" <co id="resxml8-co" linkends="resxml8"/>
tracked-correlation-id-capacity="99" <co id="resxml9-co" linkends="resxml9"/>
send-timeout="86420000" <co id="resxml10-co" linkends="resxml10"/> /&gt; </programlisting>
<para><calloutlist>
<callout arearefs="resxml1">
<callout arearefs="resxml1-co" id="resxml1">
<para>The id of the resequencer is
<emphasis>optional</emphasis>.</para>
</callout>
<callout arearefs="resxml2">
<callout arearefs="resxml2-co" id="resxml2">
<para>The input channel of the resequencer.
<emphasis>Required</emphasis>.</para>
</callout>
<callout arearefs="resxml3">
<callout arearefs="resxml3-co" id="resxml3">
<para>The channel where the resequencer will send the reordered
messages. <emphasis>Optional</emphasis>.</para>
</callout>
<callout arearefs="resxml4">
<callout arearefs="resxml4-co" id="resxml4">
<para>The channel where the resequencer will send the messages that
timed out (if <code>send-partial-result-on-timeout</code> is
<emphasis>false)</emphasis>. <emphasis>Optional</emphasis>.</para>
</callout>
<callout arearefs="resxml5">
<callout arearefs="resxml5-co" id="resxml5">
<para>Whether to send out ordered sequences as soon as they are
available, or only after the whole message group arrives.
<emphasis>Optional (true by default)</emphasis>.</para>
</callout>
<callout arearefs="resxml6">
<callout arearefs="resxml6-co" id="resxml6">
<para>The timeout for reordering message sequences (counted from the
arrival of the first message). <emphasis>Optional</emphasis>.</para>
</callout>
<callout arearefs="resxml7">
<callout arearefs="resxml7-co" id="resxml7">
<para>Whether, upon the expiration of the timeout, the ordered group
shall be sent out (even if some of the messages are missing).
<emphasis>Optional (false by default)</emphasis>.</para>
</callout>
<callout arearefs="resxml8">
<callout arearefs="resxml8-co" id="resxml8">
<para>The interval (in milliseconds) at which a reaper task is
executed, checking if there are any timed out groups.
<emphasis>Optional</emphasis>.</para>
</callout>
<callout arearefs="resxml9">
<callout arearefs="resxml9-co" id="resxml9">
<para>The capacity of the correlation id tracker. Remembers the
already processed correlation ids, preventing the formation of new
groups for messages that arrive after their group has been already
@@ -103,7 +103,7 @@
<emphasis>Optional</emphasis>.</para>
</callout>
<callout arch="" arearefs="resxml10">
<callout arearefs="resxml10-co" id="resxml10">
<para>The timeout for sending out messages.
<emphasis>Optional</emphasis>.</para>
</callout>

4
spring-integration-reference/src/resources.xml
View File

@@ -7,8 +7,8 @@
<title>Spring Integration Home</title>
<para>
The definitive source of information about Spring Integration is the
<ulink url="http://www.springframework.org/spring-integration">Spring Integration Home</ulink> at
<ulink url="http://www.springframework.org">http://www.springframework.org</ulink>. That site serves as a hub of
<ulink url="http://www.springsource.com/spring-integration">Spring Integration Home</ulink> at
<ulink url="http://www.springsource.com">http://www.springframework.org</ulink>. That site serves as a hub of
information and is the best place to find up-to-date announcements about the project as well as links to
articles, blogs, and new sample applications.
</para>

2
spring-integration-reference/src/router.xml
View File

@@ -91,7 +91,7 @@ public List&lt;String&gt; route(Foo payload) {...}</programlisting>
In addition to payload-based routing, a common requirement is to route based on metadata available within the
message header as either a property or attribute. Rather than requiring use of the
<interfacename>Message</interfacename> type as the method parameter, the <interfacename>@Router</interfacename>
annotation may also use the same @Header parameter annotation that was introduced above.
annotation may also use the @Header parameter annotation that is documented in section <xref linkend="annotations"/>.
<programlisting language="java">@Router
public List&lt;String&gt; route(@Header("orderStatus") OrderStatus status)</programlisting>
</para>

3
spring-integration-reference/src/transformer.xml
View File

@@ -57,8 +57,7 @@ Order generateOrder(String productId) {
}</programlisting>
</para>
<para>
Transformer methods may also accept the @Header and @Headers annotations. For example, one of those annotations
may complement the payload Object as an additional parameter:
Transformer methods may also accept the @Header and @Headers annotations that is documented in section <xref linkend="annotations"/>
<programlisting language="java">@Transformer
Order generateOrder(String productId, @Header("customerName") String customer) {
return new Order(productId, customer);

2
spring-integration-reference/src/xml.xml
View File

@@ -201,7 +201,7 @@
<property name="outputChannel" ref="orderItemsChannel" />
</bean>
</constructor-arg>
<constructor-arg ref="orderChannel" />
<constructor-arg ref="orderChannel" />
</bean>]]></programlisting>
</para>