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

Updated class names

Browse Source
This commit is contained in:
Mark Fisher
2008-11-03 15:34:24 +00:00
parent 74b574e6cf
commit dea26b561f
7 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -5,15 +5,15 @@
<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>ApplicationEventInboundChannelAdapter</classname>. This class in an implementation of Spring's
<classname>ApplicationEventListeningChannelAdapter</classname>. This class in 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.
</para>
<para>
To send Spring <classname>ApplicationEvents</classname>, create an instance of the
<classname>ApplicationEventPublishingMessageConsumer</classname> and register it within an endpoint. This
implementation of the <interfacename>MessageConsumer</interfacename> interface also implements Spring's
<classname>ApplicationEventPublishingMessageHandler</classname> and register it within an endpoint. This
implementation of the <interfacename>MessageHandler</interfacename> interface also implements Spring's
<interfacename>ApplicationEventPublisherAware</interfacename> interface and thus acts as a bridge between
Spring Integration Messages and <classname>ApplicationEvents</classname>.
</para>

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

@@ -15,14 +15,14 @@
transform files into strings or byte arrays.
</para>
<para>
This section will explain the workings of <classname>PollableFileSource</classname>, <classname>FileWritingMessageConsumer</classname> and how to configure them as <emphasis>beans</emphasis>. Also the support for dealing with files through file specific implementations of <interfacename>Transformer</interfacename> will be discussed. Finally the file specific namespace will be explained.
This section will explain the workings of <classname>PollableFileSource</classname>, <classname>FileWritingMessageHandler</classname> and how to configure them as <emphasis>beans</emphasis>. Also the support for dealing with files through file specific implementations of <interfacename>Transformer</interfacename> will be discussed. Finally the file specific namespace will be explained.
</para>
</section>
<section id="file-reading">
<title>Reading Files</title>
<para>
A <classname>PollableFileSource</classname> can be used to consume files from the filesystem. This is an implementation of <interfacename>PollableSource</interfacename> that creates messages from a file system directory.
A <classname>PollableFileSource</classname> can be used to consume files from the filesystem. This is an implementation of <interfacename>MessageSource</interfacename> that creates messages from a file system directory.
<programlisting language="xml"><![CDATA[<bean id="pollableFileSource" class="org.springframework.integration.file.PollableFileSource"
p:inputDirectory="file:${input.directory.property}"/>]]></programlisting>
</para>
@@ -79,7 +79,7 @@
http://www.springframework.org/schema/integration/file/spring-integration-file-1.0.xsd">
</beans>]]></programlisting>
Within this namespace you can reduce the PollableFileSource and wrap
it in a InboundChannelAdapter like this:
it in an InboundChannelAdapter like this:
<programlisting language="xml"><![CDATA[<file:inbound-channel-adapter id="filesIn"
directory="file:${input.directory.property}"/> (1)
<file:inbound-channel-adapter id="filesIn"
@@ -101,12 +101,12 @@
<title>Writing files</title>
<para>
To write messages to the file system you can use a
<classname>FileWritingMessageConsumer
<classname>FileWritingMessageHandler
</classname>
. This class can deal with File or byte[] payloads and otherwise
invokes the toString() method on the payload to estabish the contents
invokes the toString() method on the payload to establish the contents
of the File. In its simplest form the
<classname>FileWritingMessageConsumer
<classname>FileWritingMessageHandler
</classname>
just needs a parent directory for the files.
</para>
@@ -119,13 +119,13 @@
</para>
<para>
To make things easier you can configure the
FileWritingMessageConsumer as part of an outbound channel adapter
FileWritingMessageHandler as part of an outbound channel adapter
using the namespace.
<programlisting language="xml"><![CDATA[ <file:outbound-channel-adapter id="filesOut" directory="file:${input.directory.property}"/>]]></programlisting>
</para>
<para>
If you have more elaborate requirements to the payload to file
conversion you could extend the FileWritingMessageConsumer, but a
conversion you could extend the FileWritingMessageHandler, but a
much better option is to rely on a
<classname>Transformer</classname>
</para>
@@ -138,7 +138,7 @@
way around you need to do some work. Contrary to
<classname>PollableFileSource</classname>
and to a lesser extent
<classname>FileWritingMessageConsumer
<classname>FileWritingMessageHandler
</classname>
it is very likely that you will need your own mechanism to get the
job done. For this you can implement the

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

@@ -62,8 +62,8 @@
class="org.springframework.integration.httpinvoker.HttpInvokerOutboundGateway">
<property name="replyChannel" ref="replyChannel"/>
</bean>]]></programlisting>
The outbound gateway is a <interfacename>MessageConsumer</interfacename> and can therefore be registered with
either a <classname>PollingConsumerEndpoint</classname> or <classname>SubscribingConsumerEndpoint</classname>.
The outbound gateway is a <interfacename>MessageHandler</interfacename> and can therefore be registered with
either a <classname>PollingConsumer</classname> or <classname>EventDrivenConsumer</classname>.
The URL must match that defined by an inbound HttpInvoker Gateway as described in the previous section.
</para>
</section>

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

@@ -30,7 +30,7 @@
<section id="jms-outbound-channel-adapter">
<title>Outbound Channel Adapter</title>
<para>
The <classname>JmsSendingMessageConsumer</classname> implements the <interfacename>MessageConsumer</interfacename>
The <classname>JmsSendingMessageHandler</classname> implements the <interfacename>MessageHandler</interfacename>
interface and is capable of converting Spring Integration <interfacename>Messages</interfacename> to JMS messages
and then sending to a JMS destination. It requires either a 'jmsTemplate' reference or both 'connectionFactory' and
'destination' references (again, the 'destinationName' may be provided in place of the 'destination). As with the

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

@@ -7,12 +7,12 @@
<title>Mail-Sending Channel Adapter</title>
<para>
Spring Integration provides support for outbound email with the
<classname>MailSendingMessageConsumer</classname>. It delegates to a configured instance of Spring's
<classname>MailSendingMessageHandler</classname>. It delegates to a configured instance of Spring's
<interfacename>JavaMailSender</interfacename>:
<programlisting language="java"> JavaMailSender mailSender = (JavaMailSender) context.getBean("mailSender");
MailSendingMessageConsumer mailSendingConsumer = new MailSendingMessageConsumer(mailSender);</programlisting>
<classname>MailSendingMessageConsumer</classname> various mapping strategies use Spring's
MailSendingMessageHandler mailSendingHandler = new MailSendingMessageHandler(mailSender);</programlisting>
<classname>MailSendingMessageHandler</classname> various mapping strategies use Spring's
<interfacename>MailMessage</interfacename> abstraction. If the received Message's payload is already
a MailMessage instance, it will be sent directly. Therefore, it is generally recommended to precede this
consumer with a Transformer for non-trivial MailMessage construction requirements. However, a few simple

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

@@ -6,7 +6,7 @@
<section id="rmi-intro">
<title>Introduction</title>
<para>
This Chapter explains how to use RMI specific channel adapters to distribute a system over multiple jvm's. The first section will deal with sending messages over RMI. The second section shows how to receive messages over RMI. The last section shows how to define rmi channel adapters through the namespace support
This Chapter explains how to use RMI specific channel adapters to distribute a system over multiple JVMs. The first section will deal with sending messages over RMI. The second section shows how to receive messages over RMI. The last section shows how to define rmi channel adapters through the namespace support
</para>
</section>

10
spring-integration-reference/src/stream.xml
View File

@@ -36,19 +36,19 @@
<section id="stream-writing">
<title>Writing to streams</title>
<para>
For target streams, there are also two implementations: <classname>ByteStreamWritingMessageConsumer</classname> and
<classname>CharacterStreamWritingMessageConsumer</classname>. Each requires a single constructor argument -
For target streams, there are also two implementations: <classname>ByteStreamWritingMessageHandler</classname> and
<classname>CharacterStreamWritingMessageHandler</classname>. Each requires a single constructor argument -
<classname>OutputStream</classname> for byte streams or <classname>Writer</classname> for character streams,
and each provides a second constructor that adds the optional 'bufferSize'. Since both of these
ultimately implement the <interfacename>MessageConsumer</interfacename> interface, they can be referenced from a
ultimately implement the <interfacename>MessageHandler</interfacename> interface, they can be referenced from a
<emphasis>channel-adapter</emphasis> configuration as will be described in more detail in
<xref linkend="namespace-endpoint"/>.
<programlisting language="xml"><![CDATA[<bean class="org.springframework.integration.stream.ByteStreamWritingMessageConsumer">
<programlisting language="xml"><![CDATA[<bean class="org.springframework.integration.stream.ByteStreamWritingMessageHandler">
<constructor-arg ref="someOutputStream"/>
<constructor-arg value="1024"/>
</bean>
<bean class="org.springframework.integration.stream.CharacterStreamWritingMessageConsumer">
<bean class="org.springframework.integration.stream.CharacterStreamWritingMessageHandler">
<constructor-arg ref="someWriter"/>
</bean>]]>
</programlisting>