Add documentation about configuring timeouts to servicemix-ftp and servicemix-cxf-bc
git-svn-id: https://svn.apache.org/repos/asf/servicemix/documentation/trunk@1030205 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/main/webapp/jbi/components/servicemix-cxf-bc.conf b/src/main/webapp/jbi/components/servicemix-cxf-bc.conf
index 03bea95..1ada571 100644
--- a/src/main/webapp/jbi/components/servicemix-cxf-bc.conf
+++ b/src/main/webapp/jbi/components/servicemix-cxf-bc.conf
@@ -39,3 +39,91 @@
h4. Endpoint properties
{include:jbi/components/_servicemix-cxf-bc-provider.conf}
+
+h3. Examples
+h4. Configuring the CXF JMS Transport
+The ServiceMix CXF binding component also allows using the CXF JMS Transport to send and receive messages. You can use the *{{<cxf:features/>}}* element to add and configure the {{org.apache.cxf.transport.jms.JMSConfigFeature}} on the endpoint, as in the example below.
+
+{pygmentize:lang=xml}
+<cxfbc:provider wsdl="org/apache/servicemix/cxfbc/ws/security/hello_world.wsdl"
+ service="greeter:HelloWorldService"
+ endpoint="HelloWorldPortProxy"
+ interfaceName="greeter:Greeter"
+ busCfg="jms_conduit_config.xml">
+
+ <!-- add interceptors here -->
+
+ <cxfbc:features>
+ <bean class="org.apache.cxf.transport.jms.JMSConfigFeature">
+ <property name="jmsConfig">
+ <bean class="org.apache.cxf.transport.jms.JMSConfiguration">
+ <property name="concurrentConsumers">
+ <value>5</value>
+ </property>
+ <property name="connectionFactory">
+ <ref bean="myConnectionFactory" />
+ </property>
+ <property name="targetDestination">
+ <value>test.jmstransport.text.provider</value>
+ </property>
+ <property name="useJms11">
+ <value>false</value>
+ </property>
+ </bean>
+ </property>
+ </bean>
+ </cxfbc:features>
+
+</cxfbc:provider>
+
+<amq:connectionFactory id="myConnectionFactory" brokerURL="vm://localhost"/>
+{pygmentize}
+
+The {{jms_conduit_config.xml}} file specified in the {{busCfg}} parameter, is optional and can be used to specify additional JMS transport parameters:
+{pygmentize:lang=xml}
+<?xml version="1.0" encoding="UTF-8"?>
+<beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:jms="http://cxf.apache.org/transports/jms"
+ xsi:schemaLocation="
+ http://cxf.apache.org/transports/jms http://cxf.apache.org/schemas/configuration/jms.xsd
+ http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
+
+ <jms:conduit name="{http://apache.org/hello_world_soap_http}HelloWorldPort.jms-conduit" abstract="true">
+ <jms:clientConfig clientReceiveTimeout="200000"/>
+ </jms:conduit>
+
+</beans>
+{pygmentize}
+
+h4. Configuring the CXF HTTP Transport
+In order to configure the underlying HTTP transport used by a CXF BC endpoint, you can specify an additional {{busCfg}} file as in the example below.
+{pygmentize:lang=xml}
+<cxfbc:provider wsdl="org/apache/servicemix/cxfbc/ws/security/hello_world.wsdl"
+ service="greeter:HelloWorldService"
+ endpoint="HelloWorldPortProxy"
+ interfaceName="greeter:Greeter"
+ busCfg="http_conduit_config.xml">
+
+ <!-- add interceptors and additional CXF features here -->
+
+</cxfbc:provider>
+{pygmentize}
+
+The {{http_conduit_config.xml}} file can then specify the additional CXF configuration. Have a look at [this page|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html] for an overview of all the options supported by CXF.
+{pygmentize:lang=xml}
+<beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"
+ xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
+ http://cxf.apache.org/schemas/configuration/http-conf.xsd
+ http://www.springframework.org/schema/beans
+ http://www.springframework.org/schema/beans/spring-beans.xsd">
+
+ <http-conf:conduit name="{http://apache.org/hello_world_soap_http}HelloWorldPort.http-conduit">
+ <http-conf:client Connection="Keep-Alive"
+ MaxRetransmits="1"
+ AllowChunking="false" />
+ </http-conf:conduit>
+</beans>
+{pygmentize}
diff --git a/src/main/webapp/jbi/components/servicemix-ftp.conf b/src/main/webapp/jbi/components/servicemix-ftp.conf
index cd11daa..fb5d46f 100644
--- a/src/main/webapp/jbi/components/servicemix-ftp.conf
+++ b/src/main/webapp/jbi/components/servicemix-ftp.conf
@@ -28,3 +28,29 @@
h4. Endpoint properties
{include:jbi/components/_servicemix-ftp-sender.conf}
+
+h3. Examples
+
+h4. Using {{ftp:pool}} to configure the FTP connections
+
+In order to gain more control over the FTP connection parameters (active/passive, timeout, ...) that are being used, you can define your own FTP connection pool. Afterward, you can refer to the pool object from both a sender and poller endpoint.
+
+{pygmentize:lang=xml}
+<?xml version="1.0"?>
+<beans xmlns:ftp="http://servicemix.apache.org/ftp/1.0"
+ xmlns:sample="urn:servicemix:example">
+
+ <ftp:sender service="sample:sender" endpoint="endpoint"
+ uri="ftp://localhost/myfolder"
+ clientPool="#clientPool"/>
+
+ <ftp:pool id="clientPool" username="myname" password="$ecret"
+ dataTimeout="90000" />
+
+</beans>
+{pygmentize}
+
+The table below shows the full list of options offered by {{ftp:pool}}:
+{include:jbi/components/_servicemix-ftp-pool.conf}
+
+If you need even more fine-grained control over the FTP connections or the way the payloads are being handled, have a look at the [Camel FTP|http://camel.apache.org/ftp2.html] component, which offers a lot of options out of the box, but also allows setting any property on its underlying Commons NET [FTPClient|http://commons.apache.org/net/api/org/apache/commons/net/ftp/FTPClient.html] and [FTPClientConfig|http://commons.apache.org/net/api/org/apache/commons/net/ftp/FTPClientConfig.html] instances.
