diff --git a/modules/documentation/src/site/resources/css/site.css b/modules/documentation/src/site/resources/css/site.css index ffe418f6b..d06db248b 100644 --- a/modules/documentation/src/site/resources/css/site.css +++ b/modules/documentation/src/site/resources/css/site.css @@ -17,7 +17,7 @@ * under the License. */ -@import url(http://fonts.googleapis.com/css?family=Buenard); +@import url(https://fonts.googleapis.com/css?family=Buenard); body, p, div, ul, li, a, tr, td,th{ font-family: 'Buenard', serif; font-size:15px; diff --git a/modules/documentation/src/site/site.xml b/modules/documentation/src/site/site.xml index a1a54b614..3d21df2bf 100644 --- a/modules/documentation/src/site/site.xml +++ b/modules/documentation/src/site/site.xml @@ -29,10 +29,10 @@ - - - - + + + + diff --git a/modules/documentation/src/site/xdoc/dev/best-practices.xml b/modules/documentation/src/site/xdoc/dev/best-practices.xml index eb84ab1b0..9ae2561f3 100644 --- a/modules/documentation/src/site/xdoc/dev/best-practices.xml +++ b/modules/documentation/src/site/xdoc/dev/best-practices.xml @@ -52,7 +52,7 @@
  • We follow the standard - Java coding conventions + Java coding conventions published by Sun/Oracle. Please stick to these standards whenever writing code for Synapse.
    • @@ -118,10 +118,10 @@ All documentation files and samples should we well-formed XML documents.
  • - We use the Maven XDoc plugin + We use the Maven XDoc plugin to generate Synapse documentation and website. Please take some time to go through the documentation of the XDoc plugin and learn and its features. In pariculay, - you should learn the XDoc documentation format + you should learn the XDoc documentation format and use the standard XDoc tags over HTML whenever possible.
  • @@ -144,4 +144,4 @@
- \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/dev/developer-guide.xml b/modules/documentation/src/site/xdoc/dev/developer-guide.xml index 29a6b9ca4..7641798cd 100644 --- a/modules/documentation/src/site/xdoc/dev/developer-guide.xml +++ b/modules/documentation/src/site/xdoc/dev/developer-guide.xml @@ -74,21 +74,21 @@ to go through the Synapse source code in the development trunk and make contributions should use a Subversion client to interact with the Synapse code base. To learn more about using Subversion or to download the latest client distributions, please visit - the Apache Subversion project website. + the Apache Subversion project website. Developers on Unix/Linux based systems may use the command line based SVN client, while the developers on Windows platform can use an appropriate client application - like TortoiseSVN. + like TortoiseSVN.

Some useful information on using the Apache Software Foundation's source code repositories can be found among the ASF - developer documentation. + developer documentation.

Synapse development trunk is where all the latest development work takes place. This is located at - http://svn.apache.org/repos/asf/synapse/trunk/java/. + https://svn.apache.org/repos/asf/synapse/trunk/java/. Any developer with a Subversion client should be able to checkout the latest source from this SVN location but only Synapse committers are allowed to actually commit source code. Synapse committers should access the above SVN location over @@ -105,7 +105,7 @@ If you want to browse the source code of an older release of Synapse or want to implement a patch for a past release, you may checkout the relevant source tree from one of the available SVN - tags. + tags.

@@ -114,7 +114,7 @@ Synapse build system is based on Apache Maven. Either Maven2 or Maven3 can be used to build Apache Synapse from source. For information about downloading, installing, and configuring Maven, please go through - Maven project website. + Maven project website.

@@ -266,4 +266,4 @@ For Eclipse: mvn eclipse:eclipse

- \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/dev/release-process.xml b/modules/documentation/src/site/xdoc/dev/release-process.xml index 7e2b6e59f..ec444efaf 100644 --- a/modules/documentation/src/site/xdoc/dev/release-process.xml +++ b/modules/documentation/src/site/xdoc/dev/release-process.xml @@ -25,7 +25,7 @@

- We follow the standard ASF release process. + We follow the standard ASF release process. One of the committers would volunteer to play the release manager role for a given release. A few days will be spent on stabilizing the Synapse development trunk, improving its documentation and test coverage. When the code base is in a satisfactory @@ -54,9 +54,9 @@ Maven central repository requirements . Form synapse 2.1 release onwards, we follow the standard maven artifact releasing process. Most part of the release process is automated and all the required steps are listed here. - http://www.apache.org/dev/publishing-maven-artifacts.html + https://www.apache.org/dev/publishing-maven-artifacts.html

-

The details on Nexus Repository Management can be found in Repository Management with Nexus. +

The details on Nexus Repository Management can be found in Repository Management with Nexus.

@@ -74,7 +74,7 @@
  • Always run a mvn release:prepare -DdryRun=true before the actual preparation
    • @@ -82,4 +82,4 @@ - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/history.xml b/modules/documentation/src/site/xdoc/history.xml index 38b3572d8..094d5e76b 100644 --- a/modules/documentation/src/site/xdoc/history.xml +++ b/modules/documentation/src/site/xdoc/history.xml @@ -47,17 +47,17 @@ of Synapse from its humble beginnings.

    - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/index.xml b/modules/documentation/src/site/xdoc/index.xml index 278196372..cbf466890 100644 --- a/modules/documentation/src/site/xdoc/index.xml +++ b/modules/documentation/src/site/xdoc/index.xml @@ -36,14 +36,14 @@

    Apache Synapse is free and open source software distributed under the - Apache Software License 2.0. + Apache Software License 2.0. The latest version of Synapse is v3.0.1. It is a patch release which contains bug fixes and library upgrades to 3.0.0 major feature release.

    Apache Synapse, Synapse, Apache, the Apache feather logo, and the Apache Synapse - project logo are trademarks of The Apache Software + project logo are trademarks of The Apache Software Foundation

    diff --git a/modules/documentation/src/site/xdoc/userguide/config.xml b/modules/documentation/src/site/xdoc/userguide/config.xml index 1e4c53cac..fa6080680 100644 --- a/modules/documentation/src/site/xdoc/userguide/config.xml +++ b/modules/documentation/src/site/xdoc/userguide/config.xml @@ -111,7 +111,7 @@ All the functional components of the Synapse configuration are configured through XML files. The Synapse configuration language governs the XML syntax used to define and configure different types of components. This configuration language is now - available as a XML schema. + available as a XML schema.

    Typically the Synapse ESB is used to mediate the message flow between a client @@ -1099,11 +1099,11 @@ registry by specifying appropriate 'resource' elements.

    <publishWSDL key="my.wsdl"> - <resource location="http://www.standards.org/standard.wsdl" key="standard.wsdl"/> + <resource location="https://www.standards.org/standard.wsdl" key="standard.wsdl"/> </publishWSDL>

    In this example the WSDL is retrieved from the registry using the key 'my.wsdl'. It - imports another WSDL from location 'http://www.standards.org/standard.wsdl'. Instead + imports another WSDL from location 'https://www.standards.org/standard.wsdl'. Instead of loading it from this location, Synapse will retrieve the imported WSDL from the registry entry 'standard.wsdl'.

    diff --git a/modules/documentation/src/site/xdoc/userguide/deployment.xml b/modules/documentation/src/site/xdoc/userguide/deployment.xml index 511e6a68a..216a653bc 100644 --- a/modules/documentation/src/site/xdoc/userguide/deployment.xml +++ b/modules/documentation/src/site/xdoc/userguide/deployment.xml @@ -248,7 +248,7 @@ place for later reuse. One approach to overcome these difficulties is to use Maven to assemble a custom package. When used correctly, this approach solves all of the issues identified above. In particular Maven's dependency management together with - the excellent assembly plugin + the excellent assembly plugin can be used to automatically select the relevant JARs to include and pull them from Maven repositories. The remaining artifacts required to assemble the package can then be easily stored in a source control repository. @@ -258,11 +258,11 @@ only a few simple steps. To begin with, change to the directory where you want to create the project and issue the following command:

    -
    mvn archetype:generate -DarchetypeCatalog=http://synapse.apache.org
    +
    mvn archetype:generate -DarchetypeCatalog=https://synapse.apache.org

    In case of problems, you can try to use the latest version of the archetype catalog:

    -
    mvn archetype:generate -DarchetypeCatalog=http://svn.apache.org/repos/asf/synapse/trunk/java/src/site/resources
    +
    mvn archetype:generate -DarchetypeCatalog=https://svn.apache.org/repos/asf/synapse/trunk/java/src/site/resources

    Finally, if you have build Synapse from sources, you don't need to specify a catalog at all: the archetype is added automatically to the local catalog during @@ -318,7 +318,7 @@

    - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/extending.xml b/modules/documentation/src/site/xdoc/userguide/extending.xml index 31087eaeb..1628bbe6a 100644 --- a/modules/documentation/src/site/xdoc/userguide/extending.xml +++ b/modules/documentation/src/site/xdoc/userguide/extending.xml @@ -65,7 +65,7 @@

    MessageContext + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/MessageContext.java?view=markup">MessageContext Interface

    @@ -152,7 +152,7 @@ public interface MessageContext {

    Mediator + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/Mediator.java?view=markup">Mediator interface

    @@ -214,7 +214,7 @@ public interface Mediator {

    The + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/mediators/ListMediator.java?view=markup">The ListMediator interface

    @@ -277,7 +277,7 @@ public interface ListMediator extends Mediator {

    FilterMediator + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/mediators/FilterMediator.java?view=markup">FilterMediator interface

    @@ -338,7 +338,7 @@ public interface FilterMediator extends

    The + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactory.java?view=markup">The MediatorFactory interface

    @@ -366,7 +366,7 @@ public interface MediatorFactory { }

    The + href="https://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializer.java?view=markup">The MediatorSerializer interface

    @@ -409,7 +409,7 @@ public interface MediatorSerializer { Synapse loads available extensions from the runtime classpath using the J2SE + href="https://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Service%20Provider">J2SE Service Provider model . This essentially iterates over the available JAR files, for a META-INF/services directory within each file, @@ -482,4 +482,4 @@ public interface MediatorSerializer {

    - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/installation.xml b/modules/documentation/src/site/xdoc/userguide/installation.xml index 244489c48..0a5866462 100644 --- a/modules/documentation/src/site/xdoc/userguide/installation.xml +++ b/modules/documentation/src/site/xdoc/userguide/installation.xml @@ -59,14 +59,14 @@ - Java SE + Java SE Development Kit 1.6.0_23 or higher (For instructions on setting up the JDK on different operating systems, visit + href="https://www.oracle.com/technetwork/java/index.html"> Java homepage. )

    @@ -74,7 +74,7 @@ - Apache Ant - To run Synapse samples + Apache Ant - To run Synapse samples

    @@ -86,7 +86,7 @@ - Apache Maven - To + Apache Maven - To build Synapse from the source @@ -133,7 +133,7 @@

    The following distribution packages are available for download. + href="https://synapse.apache.org/download.html">download.

    1. @@ -158,7 +158,7 @@
      1. - Download Apache + Download Apache Synapse binary distribution.
      2. @@ -185,7 +185,7 @@
        1. - Download Apache + Download Apache Synapse binary distribution.
        2. @@ -213,15 +213,15 @@

          - Apache Synapse build is based on Apache + Apache Synapse build is based on Apache Maven 3. Hence, it is a prerequisite to have Maven (version 3.2.0 or later) installed in order to build Synapse from the source distribution. Instructions on - installing Maven 3 are available on the Maven + installing Maven 3 are available on the Maven website. Follow these steps to build Synapse after setting up Maven 3.

          1. - Download + Download the source distribution, which is available as a zip archive. All the necessary build scripts are included with this distribution. diff --git a/modules/documentation/src/site/xdoc/userguide/mediators.xml b/modules/documentation/src/site/xdoc/userguide/mediators.xml index 980c369b3..10be7010c 100644 --- a/modules/documentation/src/site/xdoc/userguide/mediators.xml +++ b/modules/documentation/src/site/xdoc/userguide/mediators.xml @@ -434,7 +434,7 @@ under the License. child of the SOAP body of the current message. If the validation fails, the on-fail sequence of mediators is executed. Feature elements could be used to turn on/off some of the underlying features of the schema validator (See http://xerces.apache.org/xerces2-j/features.html). + href="https://xerces.apache.org/xerces2-j/features.html">https://xerces.apache.org/xerces2-j/features.html). The schema can be specified as a static or dynamic key. When needed, imports can be specified using additional resources.

            @@ -765,7 +765,7 @@ under the License.
            <script language="js">mc.getPayloadXML()..symbol != "IBM";<script/>

            Synapse uses the Apache - Bean Scripting Framework + Bean Scripting Framework for the scripting language support, any script language supported by BSF may be used to implement a Synapse mediator.

            diff --git a/modules/documentation/src/site/xdoc/userguide/quick_start.xml b/modules/documentation/src/site/xdoc/userguide/quick_start.xml index f827a77ea..e587422a6 100644 --- a/modules/documentation/src/site/xdoc/userguide/quick_start.xml +++ b/modules/documentation/src/site/xdoc/userguide/quick_start.xml @@ -43,7 +43,7 @@ A Java runtime - JDK or JRE of version 1.6.0_23 or higher
          2. - Apache Ant http://ant.apache.org + Apache Ant http://ant.apache.org
          @@ -407,4 +407,4 @@ SOAPAction:

    - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/transports.xml b/modules/documentation/src/site/xdoc/userguide/transports.xml index f7b9089d5..779a4462c 100644 --- a/modules/documentation/src/site/xdoc/userguide/transports.xml +++ b/modules/documentation/src/site/xdoc/userguide/transports.xml @@ -51,7 +51,7 @@
  • A AMQP transport which support the AMQP protocol. - AMQP is a messaging + AMQP is a messaging protocol.
    • @@ -60,18 +60,18 @@

    The Synapse distribution also comes bundled with the following transports from - the Axis2 Transport + the Axis2 Transport project:

    • A - JMS transport + JMS transport supporting any JMS 1.0 or 1.1 provider.
    • A - Mail transport + Mail transport able to send messages using SMTP and poll messages from a POP3 or IMAP account.

      Apache Synapse is also compatible with the following transport implementations @@ -79,10 +79,10 @@

    • - TCP transport + TCP transport
    • - SMS transport + SMS transport
    • UDP transport
    • @@ -90,7 +90,7 @@

      These transports are not shipped with Apache Synapse by default and hence they should be - downloaded separately + downloaded separately from the Axis2 transport website and installed in the Synapse runtime.

      • @@ -291,7 +291,7 @@
      This parameter has the same meaning as the corresponding - mod_ssl directive + mod_ssl directive and sets the desired certificate verification level for client authentication:
      • @@ -407,8 +407,8 @@
        This is an optional parameter to validate the revocation status of the host - certificates using OCSP and - CRL when making HTTPS connections. + certificates using OCSP and + CRL when making HTTPS connections. Simply uncomment this parameter in the axis2.xml file to enable the feature. Two LRU caches are used to cache CRLs and OCSP responses until they are expired. "CacheSize" property defines the maximum size of a cache. When this limit is reached, the @@ -542,7 +542,7 @@
        This parameter has the same meaning as the corresponding - mod_ssl directive + mod_ssl directive and sets the desired certificate verification level for client authentication:
        • @@ -658,8 +658,8 @@
          This is an optional parameter to validate the revocation status of the host - certificates using OCSP and - CRL when making HTTPS connections. + certificates using OCSP and + CRL when making HTTPS connections. Simply uncomment this parameter in the axis2.xml file to enable the feature. Two LRU caches are used to cache CRLs and OCSP responses until they are expired. "CacheSize" property defines the maximum size of a cache. When this limit is reached, the @@ -689,7 +689,7 @@

          The transport is based on - Apache Commons VFS + Apache Commons VFS and supports any protocol for which a VFS provider is available. The transport is pre-configured with providers for local files ( file: @@ -884,7 +884,7 @@ </endpoint>

          Other examples of valid VFS URLs are (see - http://commons.apache.org/vfs/filesystems.html + https://commons.apache.org/vfs/filesystems.html for more samples):

            @@ -936,7 +936,7 @@ Jsch loads the list of known hosts from a file called known_hosts in the .ssh sub-directory of the user's home directory, i.e. $HOME/.ssh in Unix and %HOMEPATH%\.ssh in Windows. The location and format of this - file are compatible with the OpenSSH + file are compatible with the OpenSSH client.

            @@ -968,19 +968,19 @@

            A general overview about the FIX transport can be found in the following articles:

            To use the FIX transport, you need a local - Quickfix/J + Quickfix/J installation. Download Quickfix/J from - http://www.quickfixj.org/downloads + https://www.quickfixj.org/downloads .

            @@ -1121,8 +1121,8 @@

            AMQP transport is based on the widely used - Java AMQP client library from - RabbitMQ. + Java AMQP client library from + RabbitMQ. The client library is not distributed with Apache Synapse, and hence in order to use the AMQP transport, download the RabbitMQ Java client and copy the client library (rabbitmq-client.jar) into Synapse classpath (SYNAPSE_HOME/lib directory). @@ -1470,4 +1470,4 @@ - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/transports/fix.xml b/modules/documentation/src/site/xdoc/userguide/transports/fix.xml index d9b803c36..f63f96226 100644 --- a/modules/documentation/src/site/xdoc/userguide/transports/fix.xml +++ b/modules/documentation/src/site/xdoc/userguide/transports/fix.xml @@ -57,7 +57,7 @@

            Apache Synapse supports sending and receiving FIX messages via its FIX transport. - This transport is based on Quickfix/J, a + This transport is based on Quickfix/J, a popular open source library used to develop applications based on the FIX protocol. The FIX transport enables Synapse to operate as both a FIX acceptor and a FIX initiator. If you have some prior experience working with Quickfix/J, you will realize @@ -70,10 +70,10 @@

            @@ -81,7 +81,7 @@

            Synapse binary distribution does not contain the Quickfix/J libraries. To use the - FIX transport, you must download Quickfix/J + FIX transport, you must download Quickfix/J separately, and deploy the necessary jar files into the Synapse installation. We recommend using Quickfix/J 1.4.0 with Synapse. Copy the following jar files from the Quickfix/J binary distribution to the SYNAPSE_HOME/lib directory. @@ -152,7 +152,7 @@ specifies the URL to a file, which contains the FIX configuration for the acceptor. The URL may point to a file in the local file system or a remotely hosted file accessible over a standard protocol such as HTTP. - The file itself should be a standard .cfg file, + The file itself should be a standard .cfg file, typically used to configure FIX acceptors in Quickfix/J. Parameter is required if the proxy service should receive FIX traffic as an acceptor. @@ -169,7 +169,7 @@ specifies the URL to a file, which contains the FIX configuration for the initiator. The URL may point to a file in the local file system or a remotely hosted file accessible over a standard protocol such as HTTP. - The file itself should be a standard .cfg file, + The file itself should be a standard .cfg file, typically used to configure FIX initiators in Quickfix/J. Parameter is required if the proxy service should receive FIX traffic as an initiator. @@ -183,7 +183,7 @@ The type of message store to be used with the acceptor. Allowed values for this parameter are 'file', 'jdbc', 'memory' and 'sleepycat'. Additional - parameters + parameters required to configure the message store should be specified in the acceptor configuration file. Ignored if the proxy service is not operating in the acceptor mode. @@ -197,7 +197,7 @@ The type of message store to be used with the initiator. Allowed values for this parameter are 'file', 'jdbc', 'memory' and 'sleepycat'. Additional - parameters + parameters required to configure the message store should be specified in the initiator configuration file. Ignored if the proxy service is not operating in the initiator mode. @@ -213,7 +213,7 @@ through the acceptor. FIX messages are logged without putting them in SOAP envelopes at this level. Accepted values are 'console', 'file' and 'jdbc'. If not specified no logging will be done at the transport level. Additional - parameters + parameters required to configure each of the lof factories should be specified in the acceptor configuration file. Ignored if the proxy service is not operating in the acceptor mode. @@ -229,7 +229,7 @@ through the initiator. FIX messages are logged without putting them in SOAP envelopes at this level. Accepted values are 'console', 'file' and 'jdbc'. If not specified no logging will be done at the transport level. Additional - parameters + parameters required to configure each of the lof factories should be specified in the initiator configuration file. Ignored if the proxy service is not operating in the initiator mode. @@ -532,4 +532,4 @@

            - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/transports/nhttp.xml b/modules/documentation/src/site/xdoc/userguide/transports/nhttp.xml index 95b02f0ed..736eb9170 100644 --- a/modules/documentation/src/site/xdoc/userguide/transports/nhttp.xml +++ b/modules/documentation/src/site/xdoc/userguide/transports/nhttp.xml @@ -76,7 +76,7 @@

            The NHTTP transport is based on the Apache HTTP Core NIO library. This library is - based on the reactor pattern, + based on the reactor pattern, and the transport uses two separate I/O reactor instances:

            • @@ -369,7 +369,7 @@ All 4 values are required. Keystore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and keystores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

              @@ -406,7 +406,7 @@ All 3 values are required. Truststore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and truststores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

              @@ -432,7 +432,7 @@ Use this parameter to enable client certificate verification (client authentication). This option provides functionality similar to the - SSLVerifyClient directive + SSLVerifyClient directive of Apache HTTPD. Supported values are:
              • none: No client certificate is required
                • @@ -553,7 +553,7 @@ All 4 values are required. Keystore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and keystores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -590,7 +590,7 @@ All 3 values are required. Truststore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and truststores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -624,7 +624,7 @@
              • AllowAll
              • Strict
              - Please refer HostnameVerifier + Please refer HostnameVerifier Javadocs to learn more about this feature and the semantics of the above options. The AllowAll option essentially disables hostname verification by accepting all certificates. The Strict option requires the server @@ -711,8 +711,8 @@ CertificateRevocationVerifier Enable revocation status validation of server certificates using - OCSP and - CRL. Simply uncommenting + OCSP and + CRL. Simply uncommenting this parameter under the HTTPS sender configuration will activate the feature. Two LRU caches are used to cache CRLs and OCSP responses until they are expired. Two child XML elements are used to configure the cache @@ -751,7 +751,7 @@

              Following properties control various facets of - Apache HTTP Core, + Apache HTTP Core, the framework underlying the NHTTP transport.

              @@ -765,7 +765,7 @@ @@ -813,7 +813,7 @@ Determines whether or not I/O interest operations are to be queued and executed asynchronously by the I/O reactor thread or to be applied to the underlying - SelectionKey + SelectionKey immediately. Allowed values are either 'true' or 'false'.
              http.nio.interest-ops-queueing=false
              @@ -824,10 +824,10 @@ @@ -850,7 +850,7 @@ for incoming network I/O. This value is only a hint. When set, this is a suggestion to the OS kernel from Synapse about the size of buffers to use for the data to be received over the socket - (See SO_RCVBUF). + (See SO_RCVBUF).
              http.socket.rcv-buffer-size=4096
              @@ -863,7 +863,7 @@ for outgoing network I/O. This value is only a hint. When set, this is a suggestion to the OS kernel from Synapse about the size of buffers to use for the data to be sent over the socket - (See SO_SNDBUF). + (See SO_SNDBUF).
              http.socket.snd-buffer-size=4096
              @@ -875,7 +875,7 @@ Specifies the linger-on-close timeout duration (in milliseconds) for the sockets created by the HTTP transport. Setting to 0 or a negative value disables linger-on-close - (See SO_LINGER). + (See SO_LINGER).
              http.socket.linger=5000
              @@ -884,7 +884,7 @@ @@ -933,7 +933,7 @@ @@ -1178,4 +1178,4 @@

              [Back to top]

              - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/transports/pass_through.xml b/modules/documentation/src/site/xdoc/userguide/transports/pass_through.xml index 568c5805a..2c2f63733 100644 --- a/modules/documentation/src/site/xdoc/userguide/transports/pass_through.xml +++ b/modules/documentation/src/site/xdoc/userguide/transports/pass_through.xml @@ -67,7 +67,7 @@

              The Pass Through HTTP transport (PTHTTP transport) was developed by - WSO2 as a more efficient and more scalable + WSO2 as a more efficient and more scalable alternative to the standard Non-blocking HTTP transport (NHTTP transport) of Synapse. The PTHTTP transport was later contributed to the Synapse project, and was made the default HTTP transport of the Synapse ESB. All versions of @@ -104,7 +104,7 @@

              Similar to the NHTTP transport, the PTHTTP transport is also based on the Apache - HTTP Core NIO library. This library is based on the reactor pattern, + HTTP Core NIO library. This library is based on the reactor pattern, and the PTHTTP transport uses two separate reactor instances:

              • @@ -352,7 +352,7 @@ All 4 values are required. Keystore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and keystores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -389,7 +389,7 @@ All 3 values are required. Truststore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and truststores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -415,7 +415,7 @@
              http.socket.timeout Sets the TCP socket timeout in milliseconds - (See SO_TIMEOUT). + (See SO_TIMEOUT). This applies to sockets opened by both transport listener and sender.
              http.socket.timeout=20000
              		 http.tcp.nodelay Setting this property to 'true' disables - Nagle's algorithm + Nagle's algorithm for the HTTP connections. That is, outgoing data will not be buffered and aggregated together - (See TCP_NODELAY). + (See TCP_NODELAY).
              http.tcp.nodelay=true
              		 No No No No
              http.socket.reuseaddr - Sets the SO_REUSEADDR + Sets the SO_REUSEADDR socket option for the sockets created by the HTTP transport. Accepted values are either 'true' or 'false'.
              http.socket.reuseaddr=true
              @@ -921,7 +921,7 @@               		Specifies the action to be performed when a malformed input is detected during character set encoding or decoding. Supported values are - 'ignore', 'replace' and 'report'. See CodingErrorAction + 'ignore', 'replace' and 'report'. See CodingErrorAction for more details on each of these options.
              http.malformed.input.action=ignore
              		 Specifies the action to be performed when an un-mappable character is detected during character set encoding or decoding. Supported values are - 'ignore', 'replace' and 'report'. See CodingErrorAction + 'ignore', 'replace' and 'report'. See CodingErrorAction for more details on each of these options.
              http.malformed.input.action=ignore
              		 Use this parameter to enable client certificate verification (client authentication). This option provides functionality similar to the - SSLVerifyClient directive + SSLVerifyClient directive of Apache HTTPD. Supported values are:
              • none: No client certificate is required
                • @@ -536,7 +536,7 @@ All 4 values are required. Keystore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and keystores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -573,7 +573,7 @@ All 3 values are required. Truststore paths are resolved relative to the Synapse installation (SYNAPSE_HOME) directory. If you are not familiar with Java security and truststores, please refer - Java Cryptography Architecture + Java Cryptography Architecture specification.

                @@ -607,7 +607,7 @@
              • AllowAll
              • Strict
              - Please refer HostnameVerifier + Please refer HostnameVerifier Javadocs to learn more about this feature and the semantics of the above options. The AllowAll option essentially disables hostname verification by accepting all certificates. The Strict option requires the server @@ -694,8 +694,8 @@               		CertificateRevocationVerifier Enable revocation status validation of server certificates using - OCSP and - CRL. Simply uncommenting + OCSP and + CRL. Simply uncommenting this parameter under the HTTPS sender configuration will activate the feature. Two LRU caches are used to cache CRLs and OCSP responses until they are expired. Two child XML elements are used to configure the cache @@ -738,7 +738,7 @@

              Following properties control various facets of - Apache HTTP Core, + Apache HTTP Core, the framework underlying the Pass Through HTTP transport.

              @@ -752,7 +752,7 @@ @@ -800,7 +800,7 @@ Determines whether or not I/O interest operations are to be queued and executed asynchronously by the I/O reactor thread or to be applied to the underlying - SelectionKey + SelectionKey immediately. Allowed values are either 'true' or 'false'.
              http.nio.interest-ops-queueing=false
              @@ -811,10 +811,10 @@ @@ -837,7 +837,7 @@ for incoming network I/O. This value is only a hint. When set, this is a suggestion to the OS kernel from Synapse about the size of buffers to use for the data to be received over the socket - (See SO_RCVBUF). + (See SO_RCVBUF). If no value is specified, Synapse will use the platform (OS) default.
              http.socket.rcv-buffer-size=8192
              @@ -851,7 +851,7 @@ for outgoing network I/O. This value is only a hint. When set, this is a suggestion to the OS kernel from Synapse about the size of buffers to use for the data to be sent over the socket - (See SO_SNDBUF). + (See SO_SNDBUF). If no value is specified, Synapse will use the platform (OS) default.
              http.socket.snd-buffer-size=8192
              @@ -864,7 +864,7 @@ Specifies the linger-on-close timeout duration (in milliseconds) for the sockets created by the HTTP transport. Setting to 0 or a negative value disables linger-on-close - (See SO_LINGER). + (See SO_LINGER).
              http.socket.linger=5000
              @@ -873,7 +873,7 @@ @@ -922,7 +922,7 @@ @@ -966,7 +966,7 @@
              http.max.connection.per.target=1000
              - + @@ -1171,7 +1171,7 @@ net.ipv4.ip_local_port_range = 1024 65535 Synapse HTTP transports have some advanced logging capabilities built in to them, which can be enabled to obtain more low-level information about how the transports operate. These logging features are based on - Apache Commons Logging + Apache Commons Logging and Log4J, which constitute the logging framework used by Apache Synapse. Therefore, these features should be enabled from the SYNAPSE_HOME/lib/log4j.properties file of the installation. @@ -1708,4 +1708,4 @@ net.ipv4.ip_local_port_range = 1024 65535 - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/transports/vfs.xml b/modules/documentation/src/site/xdoc/userguide/transports/vfs.xml index fe8997b42..7653da866 100644 --- a/modules/documentation/src/site/xdoc/userguide/transports/vfs.xml +++ b/modules/documentation/src/site/xdoc/userguide/transports/vfs.xml @@ -62,7 +62,7 @@ file transfer protocols such as FTP.

              - The file transport is based on Apache Commons VFS, + The file transport is based on Apache Commons VFS, and supports all the file transfer protocols supported by Commons VFS. This includes interactions with the local file system, HTTP, HTTPS, FTP and SFTP (i.e. file transfer over SSH). @@ -252,7 +252,7 @@

              http.socket.timeout Sets the TCP socket timeout in milliseconds - (See SO_TIMEOUT). + (See SO_TIMEOUT). This applies to sockets opened by both transport listener and sender.
              http.socket.timeout=20000
              		 http.tcp.nodelay Setting this property to 'true' disables - Nagle's algorithm + Nagle's algorithm for the HTTP connections. That is, outgoing data will not be buffered and aggregated together - (See TCP_NODELAY). + (See TCP_NODELAY).
              http.tcp.nodelay=true
              		 No No
              http.socket.reuseaddr - Sets the SO_REUSEADDR + Sets the SO_REUSEADDR socket option for the sockets created by the HTTP transport. Accepted values are either 'true' or 'false'.
              http.socket.reuseaddr=true
              @@ -910,7 +910,7 @@               		Specifies the action to be performed when a malformed input is detected during character set encoding or decoding. Supported values are - 'ignore', 'replace' and 'report'. See CodingErrorAction + 'ignore', 'replace' and 'report'. See CodingErrorAction for more details on each of these options.
              http.malformed.input.action=ignore
              		 Specifies the action to be performed when an un-mappable character is detected during character set encoding or decoding. Supported values are - 'ignore', 'replace' and 'report'. See CodingErrorAction + 'ignore', 'replace' and 'report'. See CodingErrorAction for more details on each of these options.
              http.malformed.input.action=ignore
              		 NoInteger.MAX_VALUEInteger.MAX_VALUE
              http.user.agent.value transport.vfs.MoveTimestampFormat Must be a timestamp format string compatible with - java.text.SimpleDateFormat. + java.text.SimpleDateFormat. If specified, Synapse will append a timestamp in the specified format to all the file names, whenever a file is moved to a new location (i.e. when moving a file after processing it or after a failure). @@ -408,7 +408,7 @@

              Some more example file URIs are listed below. Remember to prefix each URI with the string 'vfs:' when using these to define Synapse endpoints. - Refer http://commons.apache.org/vfs/filesystems.html + Refer https://commons.apache.org/vfs/filesystems.html for a complete list of Commons VFS supported protocols and their corresponding URI formats.

              @@ -538,7 +538,7 @@

              The VFS transports supports SFTP through the - JSch + JSch library and this library also requires a list of known hosts. Since Synapse is not an interactive process, it can't request confirmation from the user and is therefore unable to automatically add a host to the list. This implies that the @@ -548,7 +548,7 @@ JSch loads the list of known hosts from a file called known_hosts in the .ssh sub-directory of the user's home directory, i.e. $HOME/.ssh in Unix and %HOMEPATH%\.ssh in Windows. The location and format of this - file are compatible with the OpenSSH + file are compatible with the OpenSSH client.

              @@ -578,4 +578,4 @@

              - \ No newline at end of file + diff --git a/modules/documentation/src/site/xdoc/userguide/upgrading.xml b/modules/documentation/src/site/xdoc/userguide/upgrading.xml index 5d27cc0a1..e9ff5ee73 100644 --- a/modules/documentation/src/site/xdoc/userguide/upgrading.xml +++ b/modules/documentation/src/site/xdoc/userguide/upgrading.xml @@ -206,7 +206,7 @@ deployment was limited to mediators bundled as simple JAR files, 1.3 extended this support to tasks and defined a new archive format (XAR) that allows to bundle these extensions together with their dependency JARs (see - SYNAPSE-377 + SYNAPSE-377 for more details). Enabling these features requires changes to the axis2.xml configuration file. In 1.2 the deployer was configured as follows:

              @@ -232,7 +232,7 @@ The way the JMS transport determines the content type of incoming messages has slightly changed between Synapse 1.2 and 2.x. The mechanism is also more flexible. See SYNAPSE-304 and SYNAPSE-424 for the reasons of this change and refer to the - WS-Commons Transport project + WS-Commons Transport project for documentation.

              @@ -401,4 +401,4 @@ - \ No newline at end of file +