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

doc polishing

Browse Source
This commit is contained in:
Mark Fisher
2010-12-16 17:38:44 -05:00
parent 6aa2a05390
commit 13447aba5a
2 changed files with 16 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/src/reference/docbook/ftp.xml
View File

@@ -76,18 +76,17 @@ xsi:schemaLocation="http://www.springframework.org/schema/integration/ftp
</bean>]]></programlisting>
</para>
<para>
Every time an adapter requests a session object from the <classname>DefaultFtpClientFactory</classname> or <classname>DefaultFtpsClientFactory</classname> the session is
returned from the default session pool maintained by these factories. Session in the session pool might go stale
(session that were disconnected by the server due to inactivity) so <classname>DefaultFtpClientFactory</classname> or <classname>DefaultFtpsClientFactory</classname>
will perform validation to make sure that they never return stale session to the adapter. If stale session was encountered
it will be removed form the pool and the new one will be created.
Every time an adapter requests a session object from its <interfacename>SessionFactory</interfacename> the session is
returned from a session pool maintained by a caching wrapper around the factory. A Session in the session pool might go stale
(if it has been disconnected by the server due to inactivity) so the <interfacename>SessionFactory</interfacename>
will perform validation to make sure that it never returns a stale session to the adapter. If a stale session was encountered,
it will be removed from the pool, and a new one will be created.
<note>
If you experience connectivity problems and would like to trace session creation as well as see which session are
polled you may enable it by setting logger to TRACE level (e.g., log4j.category.org.springframework.integration.file=TRACE)
If you experience connectivity problems and would like to trace Session creation as well as see which Sessions are
polled you may enable it by setting the logger to TRACE level (e.g., log4j.category.org.springframework.integration.file=TRACE)
</note>
</para>
</para>
<para>
Now all you need to do is inject these session factories into your adapters. Obviously the protocol (FTP or FTPS) that an adapter will

16
docs/src/reference/docbook/sftp.xml
View File

@@ -35,7 +35,7 @@ xsi:schemaLocation="http://www.springframework.org/schema/integration/sftp
the <emphasis>SFTP Session Factory</emphasis> via a regular bean definition:
Below is a basic configuration:
<programlisting language="xml"><![CDATA[<beans:bean id="sftpSessionFactory" class="org.springframework.integration.sftp.session.SftpSessionFactory">
<programlisting language="xml"><![CDATA[<beans:bean id="sftpSessionFactory" class="org.springframework.integration.sftp.session.DefaultSftpSessionFactory">
<beans:property name="host" value="loclahost"/>
<beans:property name="privateKey" value="classpath:META-INF/keys/sftpTest"/>
<beans:property name="privateKeyPassphrase" value="springIntegration"/>
@@ -44,14 +44,14 @@ xsi:schemaLocation="http://www.springframework.org/schema/integration/sftp
</beans:bean>]]></programlisting>
<para>
Every time an adapter requests a session object from the <classname>SftpSessionFactory</classname> the session is
returned from the default session pool maintained by the factory. Session in the session pool might go stale
(session that were disconnected by the server due to inactivity) so <classname>SftpSessionFactory</classname>
will perform validation to make sure that it never returns stale session to the adapter. If stale session was encountered
it will be removed form the pool and the new one will be created.
Every time an adapter requests a session object from its <interfacename>SessionFactory</interfacename> the session is
returned from a session pool maintained by a caching wrapper around the factory. A Session in the session pool might go stale
(if it has been disconnected by the server due to inactivity) so the <interfacename>SessionFactory</interfacename>
will perform validation to make sure that it never returns a stale session to the adapter. If a stale session was encountered,
it will be removed from the pool, and a new one will be created.
<note>
If you experience connectivity problems and would like to trace session creation as well as see which session are
polled you may enable it by setting logger to TRACE level (e.g., log4j.category.org.springframework.integration.file=TRACE)
If you experience connectivity problems and would like to trace Session creation as well as see which Sessions are
polled you may enable it by setting the logger to TRACE level (e.g., log4j.category.org.springframework.integration.file=TRACE)
</note>
</para>