camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r901542 [6/8] - in /websites/production/camel/content: ./ cache/
Date Fri, 14 Mar 2014 10:20:21 GMT
Modified: websites/production/camel/content/crypto.html
==============================================================================
--- websites/production/camel/content/crypto.html (original)
+++ websites/production/camel/content/crypto.html Fri Mar 14 10:20:20 2014
@@ -86,7 +86,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Crypto-Crypto">Crypto</h2><p><strong>Available as of Camel 2.3</strong><br clear="none"> <strong>PGP Available as of Camel 2.9</strong></p><p>The Crypto <a shape="rect" href="data-format.html">Data Format</a> integrates the Java Cryptographic Extension into Camel, allowing simple and flexible encryption and decryption of messages using Camel's familiar marshall and unmarshal formatting mechanism. It assumes marshalling to mean encryption to cyphertext and unmarshalling to mean decryption back to the original plaintext. This data format implements only symmetric (shared-key) encryption and decyption.</p><h3 id="Crypto-Options">Options</h3><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Descri
 ption </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>DES/CBC/PKCS5Padding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JCE algorithm name indicating the cryptographic algorithm that will be used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithmParameterSpec</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>java.security.spec.AlgorithmParameterSpec</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A JCE AlgorithmParameterSpec used to initialize the Cipher. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p> <code>Integer</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>2048</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the size of the buffer used in the signature process. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cryptoProvider</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the JCE Security Provider that should be used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initializationVector</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A byte array containing the Initialization Vector that will be 
 used to initialize the Cipher. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>inline</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Flag indicating that the configured IV should be inlined into the encrypted data stream. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>macAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JCE algorithm name indicating the Message Authentication algorithm. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>shouldAppendHMAC</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <cod
 e>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Flag indicating that a Message Authentication Code should be calculated and appended to the encrypted data.</p></td></tr></tbody></table>
+<div class="wiki-content maincontent"><h2 id="Crypto-Crypto">Crypto</h2><p><strong>Available as of Camel 2.3</strong><br clear="none"> <strong>PGP Available as of Camel 2.9</strong></p><p>The Crypto <a shape="rect" href="data-format.html">Data Format</a> integrates the Java Cryptographic Extension into Camel, allowing simple and flexible encryption and decryption of messages using Camel's familiar marshall and unmarshal formatting mechanism. It assumes marshalling to mean encryption to cyphertext and unmarshalling to mean decryption back to the original plaintext. This data format implements only symmetric (shared-key) encryption and decyption.</p><h3 id="Crypto-Options">Options</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="
 confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>DES/CBC/PKCS5Padding</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JCE algorithm name indicating the cryptographic algorithm that will be used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithmParameterSpec</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>java.security.spec.AlgorithmParameterSpec</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A JCE AlgorithmParameterSpec used to initialize the Cipher. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan
 ="1" class="confluenceTd"><p> <code>Integer</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>2048</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the size of the buffer used in the signature process. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cryptoProvider</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the JCE Security Provider that should be used. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initializationVector</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A byte array containing the Initializat
 ion Vector that will be used to initialize the Cipher. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>inline</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Flag indicating that the configured IV should be inlined into the encrypted data stream. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>macAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JCE algorithm name indicating the Message Authentication algorithm. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>shouldAppendHMAC</code> </p></td><td colspan="1" rowspan="1" class
 ="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Flag indicating that a Message Authentication Code should be calculated and appended to the encrypted data.</p></td></tr></tbody></table></div>
 <h3 id="Crypto-BasicUsage">Basic Usage</h3><p>At its most basic all that is required to encrypt/decrypt an exchange is a shared secret key. If one or more instances of the Crypto data format are configured with this key the format can be used to encrypt the payload in one route (or part of one) and decrypted in another. For example, using the Java DSL as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 KeyGenerator generator = KeyGenerator.getInstance(&quot;DES&quot;);
@@ -231,10 +231,10 @@ from(&quot;direct:key-in-header-decrypt&
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;crypto id=&quot;nokey&quot; algorithm=&quot;DES&quot; /&gt;
 ]]></script>
-</div></div><h3 id="Crypto-PGPDataFormatOptions">PGPDataFormat Options</h3><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyUserid</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The user ID of the key in the PGP keyring used during encryption. See also option <code>keyUserids</code>. Can also be only a part of a user ID. For example, if the user ID is "Test User &lt;test@camel.com&gt;" then you can use the part "Test User" or "&lt;test@camel.com&gt;" to address the u
 ser ID. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyUserids</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>List&lt;String&gt;</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>: PGP allows to encrypt the symmetric key by several asymmetric public receiver keys. You can specify here the User IDs or parts of User IDs of several public keys contained in the PGP keyring.  If you just have one User ID, then you can also use the option <code>keyUserid</code>. The User ID specified in <code>keyUserid</code> and the User IDs in <code>keyUserids</code> will be merged together and the corresponding public keys will be used for the encryption. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>password</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <co
 de>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password used when opening the private key (not used for encryption). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyFileName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system by using the "file:" prefix). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>encryptionKeyRing</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1
 " class="confluenceTd"><p> <strong>Since camel 2.12.1</strong>; encryption keyring; you can not set the keyFileName and encryptionKeyRing at the same time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyUserid</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). During the signature verification process the specified User ID restricts the public keys from the public keyring which can be used for the verification. If no User ID is specified for the signature verficiation then any public key in the public keyring can be used for the verification. Can also be only a part of a user ID. For example, if the 
 user ID is "Test User &lt;test@camel.com&gt;" then you can use the part "Test User" or "&lt;test@camel.com&gt;" to address the User ID. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyUserids</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>List&lt;String&gt;</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.12.3</strong>; optional list of User IDs of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). You can specify here the User IDs or parts of User IDs of several keys contained in the PGP keyring.  If you just have one User ID, then you can also use the option <code>keyUserid</code>. The User ID specified in <code>keyUserid</code> and the User IDs in <code>keyUserids</code> will be merged together and the corresponding keys will be used
  for the signing or signature verification. If the specified User IDs reference several keys then for each key a signature is added to the PGP result during the encryption-signing process. In the decryption-verifying process the list of User IDs restricts the list of public keys which can be used for signature verification. If the list of User IDs is empty then any public key in the public keyring can be used for the signature verification.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signaturePassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional password used when opening the private key used for signing (during encryption). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyFileName<
 /code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must be accessible as a classpath resource (but you can specify a location in the file system by using the "file:" prefix). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyRing</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.1</strong>; signature keyring; you can not set the signatureKeyFileName and signatureKeyRing at the same time. </p></td></tr><tr><td
  colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>SymmetricKeyAlgorithmTags.CAST5</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>; symmetric key encryption algorithm; possible values are defined in <code>org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags</code>; for example 2 (= TRIPLE DES), 3 (= CAST5), 4 (= BLOWFISH), 6 (= DES), 7 (= AES_128). Only relevant for encrypting. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>compressionAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CompressionAlgorithmTags.ZIP</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>; compress
 ion algorithm; possible values are defined in <code>org.bouncycastle.bcpg.CompressionAlgorithmTags</code>; for example 0 (= UNCOMPRESSED), 1 (= ZIP), 2 (= ZLIB), 3 (= BZIP2). Only relevant for encrypting. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>hashAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HashAlgorithmTags.SHA1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>: signature hash algorithm; possible values are defined in <code>org.bouncycastle.bcpg.HashAlgorithmTags</code>; for example 2 (= SHA1), 8 (= SHA256), 9 (= SHA384), 10 (= SHA512), 11 (=SHA224). Only relevant for signing. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>armored</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1"
  rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> This option will cause PGP to base64 encode the encrypted text, making it available for copy/paste, etc. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>integrity</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Adds an integrity check/sign into the encryption file. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>passphraseAccessor</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/converter/crypto/PGPPassphraseAccessor.java" rel="nofollow">PGPPassphraseAccessor</a> </p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.12.2</strong>; provides passphrases corresponding to user Ids.  If no passpharase can be found from the option <code>password</code> or <code>signaturePassword</code> and from the headers <code>CamelPGPDataFormatKeyPassword</code> or <code>CamelPGPDataFormatSignatureKeyPassword</code> then the passphrase is fetched from the passphrase accessor. You provide a bean which implements the interface <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/converter/crypto/PGPPassphraseAccessor.java" rel="nofollow">PGPPassphraseAccessor</a>. A default implementation is given by <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/converter/crypto/DefaultPGPPass
 phraseAccessor.java" rel="nofollow">DefaultPGPPassphraseAccessor</a>.  The passphrase accessor is especially useful in the decrypt case; see chapter 'PGP Decrypting/Verifying of Messages Encrypted/Signed by Different Private/Public Keys'  below. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureVerificationOption</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>"optional"</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.13.0</strong>: controls the behavior for verifying the signature during unmarshaling. There are three values possible:</p>
+</div></div><h3 id="Crypto-PGPDataFormatOptions">PGPDataFormat Options</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyUserid</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The user ID of the key in the PGP keyring used during encryption. See also option <code>keyUserids</code>. Can also be only a part of a user ID. For example, if the user ID is "Test User &lt;test@camel.com&gt;" then you can use the part "Test User" or "&lt;test@camel.c
 om&gt;" to address the user ID. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyUserids</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>List&lt;String&gt;</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>: PGP allows to encrypt the symmetric key by several asymmetric public receiver keys. You can specify here the User IDs or parts of User IDs of several public keys contained in the PGP keyring.  If you just have one User ID, then you can also use the option <code>keyUserid</code>. The User ID specified in <code>keyUserid</code> and the User IDs in <code>keyUserids</code> will be merged together and the corresponding public keys will be used for the encryption. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>password</code> </p></td><td colspan="1" rowspan="1" clas
 s="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password used when opening the private key (not used for encryption). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyFileName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system by using the "file:" prefix). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>encryptionKeyRing</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><t
 d colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.1</strong>; encryption keyring; you can not set the keyFileName and encryptionKeyRing at the same time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyUserid</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). During the signature verification process the specified User ID restricts the public keys from the public keyring which can be used for the verification. If no User ID is specified for the signature verficiation then any public key in the public keyring can be used for the verification. Can also be only a part of a user 
 ID. For example, if the user ID is "Test User &lt;test@camel.com&gt;" then you can use the part "Test User" or "&lt;test@camel.com&gt;" to address the User ID. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyUserids</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>List&lt;String&gt;</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.12.3</strong>; optional list of User IDs of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). You can specify here the User IDs or parts of User IDs of several keys contained in the PGP keyring.  If you just have one User ID, then you can also use the option <code>keyUserid</code>. The User ID specified in <code>keyUserid</code> and the User IDs in <code>keyUserids</code> will be merged together and the corresp
 onding keys will be used for the signing or signature verification. If the specified User IDs reference several keys then for each key a signature is added to the PGP result during the encryption-signing process. In the decryption-verifying process the list of User IDs restricts the list of public keys which can be used for signature verification. If the list of User IDs is empty then any public key in the public keyring can be used for the signature verification.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signaturePassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional password used when opening the private key used for signing (during encryption). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <co
 de>signatureKeyFileName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.11.0</strong>; optional filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must be accessible as a classpath resource (but you can specify a location in the file system by using the "file:" prefix). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureKeyRing</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>byte[]</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.1</strong>; signature keyring; you can not set the signatureKeyFileName and signatureKeyRing at the same tim
 e. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>algorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>SymmetricKeyAlgorithmTags.CAST5</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>; symmetric key encryption algorithm; possible values are defined in <code>org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags</code>; for example 2 (= TRIPLE DES), 3 (= CAST5), 4 (= BLOWFISH), 6 (= DES), 7 (= AES_128). Only relevant for encrypting. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>compressionAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CompressionAlgorithmTags.ZIP</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2
 .12.2</strong>; compression algorithm; possible values are defined in <code>org.bouncycastle.bcpg.CompressionAlgorithmTags</code>; for example 0 (= UNCOMPRESSED), 1 (= ZIP), 2 (= ZLIB), 3 (= BZIP2). Only relevant for encrypting. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>hashAlgorithm</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>int</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HashAlgorithmTags.SHA1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.12.2</strong>: signature hash algorithm; possible values are defined in <code>org.bouncycastle.bcpg.HashAlgorithmTags</code>; for example 2 (= SHA1), 8 (= SHA256), 9 (= SHA384), 10 (= SHA512), 11 (=SHA224). Only relevant for signing. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>armored</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> 
 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> This option will cause PGP to base64 encode the encrypted text, making it available for copy/paste, etc. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>integrity</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Adds an integrity check/sign into the encryption file. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>passphraseAccessor</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/converter/crypto/PGPPassphraseAccessor.java" rel="nofollow">PGPPass
 phraseAccessor</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since Camel 2.12.2</strong>; provides passphrases corresponding to user Ids.  If no passpharase can be found from the option <code>password</code> or <code>signaturePassword</code> and from the headers <code>CamelPGPDataFormatKeyPassword</code> or <code>CamelPGPDataFormatSignatureKeyPassword</code> then the passphrase is fetched from the passphrase accessor. You provide a bean which implements the interface <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/converter/crypto/PGPPassphraseAccessor.java" rel="nofollow">PGPPassphraseAccessor</a>. A default implementation is given by <a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-crypto/src/main/java/org/apache/camel/convert
 er/crypto/DefaultPGPPassphraseAccessor.java" rel="nofollow">DefaultPGPPassphraseAccessor</a>.  The passphrase accessor is especially useful in the decrypt case; see chapter 'PGP Decrypting/Verifying of Messages Encrypted/Signed by Different Private/Public Keys'  below. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>signatureVerificationOption</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>"optional"</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Since camel 2.13.0</strong>: controls the behavior for verifying the signature during unmarshaling. There are three values possible:</p>
 <ul><li><code>"optional"</code>: The PGP message may or may not contain signatures; if it does contain signatures, then a signature verification is executed. Use the constant PGPKeyAccessDataFormat.SIGNATURE_VERIFICATION_OPTION_OPTIONAL.</li><li><code>"required"</code>: The PGP message must contain at least one signature; if this is not the case an exception (PGPException) is thrown.  A signature verification is executed. Use the constant PGPKeyAccessDataFormat.SIGNATURE_VERIFICATION_OPTION_REQUIRED.</li><li><code>"ignore"</code>: Contained signatures in the PGP message are ignored; no signature verification is executed. Use the constant PGPKeyAccessDataFormat.SIGNATURE_VERIFICATION_OPTION_IGNORE.</li><li><code>"no_signature_allowed"</code>: The PGP message must not contain a signature; otherwize an exception (PGPException) is thrown. Use the constant PGPKeyAccessDataFormat.SIGNATURE_VERIFICATION_OPTION_NO_SIGNATURE_ALLOWED.</li></ul>
-</td></tr></tbody></table>
-<h3 id="Crypto-PGPDataFormatMessageHeaders">PGPDataFormat Message Headers</h3><p>You can override the PGPDataFormat options by applying below headers into message dynamically.</p>&#160;<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyFileName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; filename of the keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatEncryptionKeyRing</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><
 p><code>byte[]</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.1</strong>; the encryption keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyUserid</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; the User ID of the key in the PGP keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyUserids</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>List&lt;String&gt;</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since camel 2.12.2</strong>: the User IDs of the key in the PGP keyring; will override existing setting directly on the PGPDataFo
 rmat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyPassword</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; password used when opening the private key; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyFileName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; filename of the signature keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyRing</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>byte[]</code></p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.1</strong>; the signature keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyUserid</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; the User ID of the signature key in the PGP keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CamelPGPDataFormatSignatureKeyUserids</td><td colspan="1" rowspan="1" class="confluenceTd">List&lt;String&gt;</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since Camel 2.12.3</strong>; the User IDs of the signature keys in the PGP keyring; will override existing setting directly on the PGPDataFormat.</td></tr><tr><td colspan=
 "1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyPassword</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; password used when opening the signature private key; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatEncryptionAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; symmetric key encryption algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureHashAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan=
 "1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; signature hash algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatCompressionAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; compression algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CamelPGPDataFormatNumberOfEncryptionKeys</td><td colspan="1" rowspan="1" class="confluenceTd">Integer</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since</strong>&#160;<strong>Camel 2.12.3;&#160; </strong>number of public keys used for encrypting the symmectric key, set by PGPDataFormat during encryptiion process</td></tr><tr><td colspan="1" rowspan="1" class="confluen
 ceTd">CamelPGPDataFormatNumberOfSigningKeys</td><td colspan="1" rowspan="1" class="confluenceTd">Integer</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since</strong>&#160;<strong>Camel 2.12.3; </strong>number of private keys used for creating signatures, set by PGPDataFormat during signing process</td></tr></tbody></table></div><h3 id="Crypto-EncryptingwithPGPDataFormat">Encrypting with PGPDataFormat</h3><p>The following sample uses the popular PGP format for encrypting/decrypting files using the <a shape="rect" class="external-link" href="http://www.bouncycastle.org/java.html" rel="nofollow">Bouncy Castle Java libraries</a>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</td></tr></tbody></table></div>
+<h3 id="Crypto-PGPDataFormatMessageHeaders">PGPDataFormat Message Headers</h3><p>You can override the PGPDataFormat options by applying below headers into message dynamically.</p><p>&#160;</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyFileName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; filename of the keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatEncryptionKeyRing</code></p></td><td colspan="1" rowspan="1" class="confluen
 ceTd"><p><code>byte[]</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.1</strong>; the encryption keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyUserid</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; the User ID of the key in the PGP keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyUserids</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>List&lt;String&gt;</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since camel 2.12.2</strong>: the User IDs of the key in the PGP keyring; will override existing setting directly on the PG
 PDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatKeyPassword</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; password used when opening the private key; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyFileName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; filename of the signature keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyRing</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>byte[]</cod
 e></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.1</strong>; the signature keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyUserid</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; the User ID of the signature key in the PGP keyring; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CamelPGPDataFormatSignatureKeyUserids</td><td colspan="1" rowspan="1" class="confluenceTd">List&lt;String&gt;</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since Camel 2.12.3</strong>; the User IDs of the signature keys in the PGP keyring; will override existing setting directly on the PGPDataFormat.</td></tr><tr><td c
 olspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureKeyPassword</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.11.0</strong>; password used when opening the signature private key; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatEncryptionAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; symmetric key encryption algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatSignatureHashAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td c
 olspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; signature hash algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelPGPDataFormatCompressionAlgorithm</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Since Camel 2.12.2</strong>; compression algorithm; will override existing setting directly on the PGPDataFormat.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CamelPGPDataFormatNumberOfEncryptionKeys</td><td colspan="1" rowspan="1" class="confluenceTd">Integer</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since</strong>&#160;<strong>Camel 2.12.3;&#160; </strong>number of public keys used for encrypting the symmectric key, set by PGPDataFormat during encryptiion process</td></tr><tr><td colspan="1" rowspan="1" class="c
 onfluenceTd">CamelPGPDataFormatNumberOfSigningKeys</td><td colspan="1" rowspan="1" class="confluenceTd">Integer</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Since</strong>&#160;<strong>Camel 2.12.3; </strong>number of private keys used for creating signatures, set by PGPDataFormat during signing process</td></tr></tbody></table></div><h3 id="Crypto-EncryptingwithPGPDataFormat">Encrypting with PGPDataFormat</h3><p>The following sample uses the popular PGP format for encrypting/decrypting files using the <a shape="rect" class="external-link" href="http://www.bouncycastle.org/java.html" rel="nofollow">Bouncy Castle Java libraries</a>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 // Public Key FileName
 String keyFileName = getKeyFileName();

Modified: websites/production/camel/content/cxf.html
==============================================================================
--- websites/production/camel/content/cxf.html (original)
+++ websites/production/camel/content/cxf.html Fri Mar 14 10:20:20 2014
@@ -99,11 +99,11 @@
                     </div>
     </div>
 <p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1393618782193 {padding: 0px;}
-div.rbtoc1393618782193 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1393618782193 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1394792314208 {padding: 0px;}
+div.rbtoc1394792314208 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1394792314208 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1393618782193">
+/*]]>*/</style></p><div class="toc-macro rbtoc1394792314208">
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>

Modified: websites/production/camel/content/hdfs.html
==============================================================================
--- websites/production/camel/content/hdfs.html (original)
+++ websites/production/camel/content/hdfs.html Fri Mar 14 10:20:20 2014
@@ -86,94 +86,31 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="HDFS-HDFSComponent">HDFS Component</h2>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>The <strong>hdfs</strong> component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of <a shape="rect" class="external-link" href="http://hadoop.apache.org">Hadoop</a>.</p>
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;dependency&gt;
+<div class="wiki-content maincontent"><h2 id="HDFS-HDFSComponent">HDFS Component</h2><p><strong>Available as of Camel 2.8</strong></p><p>The <strong>hdfs</strong> component enables you to read and write messages from/to an HDFS file system. HDFS is the distributed file system at the heart of <a shape="rect" class="external-link" href="http://hadoop.apache.org">Hadoop</a>.</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-hdfs&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="HDFS-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-hdfs://hostname[:port][/path][?options]
+</div></div><h3 id="HDFS-URIformat">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[hdfs://hostname[:port][/path][?options]
 ]]></script>
-</div></div>
-
-<p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code><br clear="none">
-The path is treated in the following way:</p>
-<ol><li>as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.</li><li>as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named using the configured <a shape="rect" href="uuidgenerator.html">uuidgenerator</a>.</li></ol>
-
-
-<h3 id="HDFS-Options">Options</h3>
-<div class="confluenceTableSmall">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr></tbody></table>
-</div>
-
-<h4 id="HDFS-KeyTypeandValueType">KeyType and ValueType</h4>
-<ul><li>NULL it means that the key or the value is absent</li><li>BYTE for writing a byte, the java Byte class is mapped into a BYTE</li><li>BYTES for writing a sequence of bytes. It maps the java ByteBuffer class</li><li>INT for writing java integer</li><li>FLOAT for writing java float</li><li>LONG for writing java long</li><li>DOUBLE for writing java double</li><li>TEXT for writing java strings</li></ul>
-
-
-<p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p>
-
-<h3 id="HDFS-SplittingStrategy">Splitting Strategy</h3>
-<p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p>
-<ul><li>If the split strategy option has been defined, the hdfs path will be used as a directory and files will be created using the configured <a shape="rect" href="uuidgenerator.html">uuidgenerator</a></li><li>Every time a splitting condition is met, a new file is created.<br clear="none">
-The splitStrategy option is defined as a string with the following syntax:<br clear="none">
-splitStrategy=&lt;ST&gt;:&lt;value&gt;,&lt;ST&gt;:&lt;value&gt;,*</li></ul>
-
-
-<p>where &lt;ST&gt; can be:</p>
-<ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than &lt;value&gt;</li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than &lt;value&gt;</li><li>IDLE a new file is created, and the old is closed when no writing happened in the last &lt;value&gt; milliseconds</li></ul>
-
-
-    <div class="aui-message warning shadowed information-macro">
+</div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code><br clear="none"> The path is treated in the following way:</p><ol><li>as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.</li><li>as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a>.</li></ol><h3 id="HDFS-Options">Options</h3><div class="confluenceTableSmall">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>owner</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13/2.12.4:</strong> The file
  owner must match this owner for the consumer to pickup the file. Otherwise the file is skipped. </p></td></tr></tbody></table>
+</div><h4 id="HDFS-KeyTypeandValueType">KeyType and ValueType</h4><ul><li>NULL it means that the key or the value is absent</li><li>BYTE for writing a byte, the java Byte class is mapped into a BYTE</li><li>BYTES for writing a sequence of bytes. It maps the java ByteBuffer class</li><li>INT for writing java integer</li><li>FLOAT for writing java float</li><li>LONG for writing java long</li><li>DOUBLE for writing java double</li><li>TEXT for writing java strings</li></ul><p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p><h3 id="HDFS-SplittingStrategy">Splitting Strategy</h3><p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p><ul><li>If the split strategy option ha
 s been defined, the hdfs path will be used as a directory and files will be created using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a></li><li>Every time a splitting condition is met, a new file is created.<br clear="none"> The splitStrategy option is defined as a string with the following syntax:<br clear="none"> splitStrategy=&lt;ST&gt;:&lt;value&gt;,&lt;ST&gt;:&lt;value&gt;,*</li></ul><p>where &lt;ST&gt; can be:</p><ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than &lt;value&gt;</li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than &lt;value&gt;</li><li>IDLE a new file is created, and the old is closed when no writing happened in the last &lt;value&gt; milliseconds</li></ul>    <div class="aui-message warning shadowed information-macro">
                             <span class="aui-icon icon-warning">Icon</span>
                 <div class="message-content">
-                            
-<p>note that this strategy currently requires either setting an IDLE value or setting the HdfsConstants.HDFS_CLOSE header to false to use the BYTES/MESSAGES configuration...otherwise, the file will be closed with each message</p>
+                            <p>note that this strategy currently requires either setting an IDLE value or setting the HdfsConstants.HDFS_CLOSE header to false to use the BYTES/MESSAGES configuration...otherwise, the file will be closed with each message</p>
                     </div>
     </div>
-
-
-<p>for example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
+<p>for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
 ]]></script>
-</div></div>
-<p>it means: a new file is created either when it has been idle for more than 1 second or if more than 5 bytes have been written. So, running <code>hadoop fs -ls /tmp/simple-file</code> you'll see that multiple files have been created.</p>
-
-<h3 id="HDFS-MessageHeaders">Message Headers</h3>
-
-<p>The following headers are supported by this component:</p>
-
-<h4 id="HDFS-Produceronly">Producer only</h4>
-<div class="confluenceTableSmall">
+</div></div><p>it means: a new file is created either when it has been idle for more than 1 second or if more than 5 bytes have been written. So, running <code>hadoop fs -ls /tmp/simple-file</code> you'll see that multiple files have been created.</p><h3 id="HDFS-MessageHeaders">Message Headers</h3><p>The following headers are supported by this component:</p><h4 id="HDFS-Produceronly">Producer only</h4><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelFileName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13:</strong> Specifies the name of the file to write (relative to the endpoint path). The name can be a <code>String</code> or an <a shape="rect" href="expression.html" title="Expression">Expression</a> object. Only relevant when not using a split strategy. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="HDFS-Controllingtoclosefilestream">Controlling to close file stream</h3>
-<p><strong>Available as of Camel 2.10.4</strong></p>
-
-<p>When using the <a shape="rect" href="hdfs.html">HDFS</a> producer <strong>without</strong> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <code>HdfsConstants.HDFS_CLOSE</code> (value = <code>"CamelHdfsClose"</code>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p>
-
-<p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p>
-
-
-<h3 id="HDFS-UsingthiscomponentinOSGi">Using this component in OSGi</h3>
-<p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context class loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p></div>
+</div><h3 id="HDFS-Controllingtoclosefilestream">Controlling to close file stream</h3><p><strong>Available as of Camel 2.10.4</strong></p><p>When using the <a shape="rect" href="hdfs.html">HDFS</a> producer <strong>without</strong> a split strategy, then the file output stream is by default closed after the write. However you may want to keep the stream open, and only explicitly close the stream later. For that you can use the header <code>HdfsConstants.HDFS_CLOSE</code> (value = <code>"CamelHdfsClose"</code>) to control this. Setting this value to a boolean allows you to explicit control whether the stream should be closed or not.</p><p>Notice this does not apply if you use a split strategy, as there are various strategies that can control when the stream is closed.</p><h3 id="HDFS-UsingthiscomponentinOSGi">Using this component in OSGi</h3><p>This component is fully functional in an OSGi environment, however, it requires some actions from the user. Hadoop uses the thread context cl
 ass loader in order to load resources. Usually, the thread context classloader will be the bundle class loader of the bundle that contains the routes. So, the default configuration files need to be visible from the bundle class loader. A typical way to deal with it is to keep a copy of core-default.xml in your bundle root. That file can be found in the hadoop-common.jar.</p></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/camel/content/hdfs2.html
==============================================================================
--- websites/production/camel/content/hdfs2.html (original)
+++ websites/production/camel/content/hdfs2.html Fri Mar 14 10:20:20 2014
@@ -98,7 +98,7 @@
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[hdfs2://hostname[:port][/path][?options]
 ]]></script>
 </div></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code><br clear="none"> The path is treated in the following way:</p><ol><li>as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.</li><li>as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a>.</li></ol><h3 id="HDFS2-Options">Options</h3><div class="confluenceTableSmall">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>overwrite</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file can be overwritten </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>append</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Append to existing file. Notice that not all HDFS file systems support the append option. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>bufferSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The buffer size used by HDFS  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>replication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The HDFS replication factor  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>blockSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>67108864</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The size of the HDFS blocks  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>fileType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NORMAL_FILE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>fileSystemType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>HDFS</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> It can be LOCAL for local filesystem  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>NULL</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>valueType</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>TEXT</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The type for the key in case of sequence or map files. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>splitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluence
 Td"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A string describing the strategy on how to split the file based on different criteria. See below.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>openedSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>opened</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When a file is opened for reading/writing the file is renamed with this suffix to avoid to read it during the writing phase. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>readSuffix</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>read</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Once the file has been read is renamed with this suffix to avoid to read it again.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>initialDelay</code> </p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For the consumer, how much to wait (milliseconds) before to start scanning the directory.  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>delay</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The interval (milliseconds) between the directory scans. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>pattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>*</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The pattern used for scanning the directory  </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>chunkSize</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>4096</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When rea
 ding a normal file, this is split into chunks producing a message per chunk. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectOnStartup</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.3/2.10.1:</strong> Whether to connect to the HDFS file system on starting the producer/consumer. If <code>false</code> then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to <code>false</code> allows your application to startup, and not block for up till 15 minutes. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>owner</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The file owner must match this owner for the
  consumer to pickup the file. Otherwise the file is skipped. </p></td></tr></tbody></table>
 </div><h4 id="HDFS2-KeyTypeandValueType">KeyType and ValueType</h4><ul><li>NULL it means that the key or the value is absent</li><li>BYTE for writing a byte, the java Byte class is mapped into a BYTE</li><li>BYTES for writing a sequence of bytes. It maps the java ByteBuffer class</li><li>INT for writing java integer</li><li>FLOAT for writing java float</li><li>LONG for writing java long</li><li>DOUBLE for writing java double</li><li>TEXT for writing java strings</li></ul><p>BYTES is also used with everything else, for example, in Camel a file is sent around as an InputStream, int this case is written in a sequence file or a map file as a sequence of bytes.</p><h3 id="HDFS2-SplittingStrategy">Splitting Strategy</h3><p>In the current version of Hadoop opening a file in append mode is disabled since it's not very reliable. So, for the moment, it's only possible to create new files. The Camel HDFS endpoint tries to solve this problem in this way:</p><ul><li>If the split strategy option 
 has been defined, the hdfs path will be used as a directory and files will be created using the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a></li><li>Every time a splitting condition is met, a new file is created.<br clear="none"> The splitStrategy option is defined as a string with the following syntax:<br clear="none"> splitStrategy=&lt;ST&gt;:&lt;value&gt;,&lt;ST&gt;:&lt;value&gt;,*</li></ul><p>where &lt;ST&gt; can be:</p><ul><li>BYTES a new file is created, and the old is closed when the number of written bytes is more than &lt;value&gt;</li><li>MESSAGES a new file is created, and the old is closed when the number of written messages is more than &lt;value&gt;</li><li>IDLE a new file is created, and the old is closed when no writing happened in the last &lt;value&gt; milliseconds</li></ul>    <div class="aui-message warning shadowed information-macro">
                             <span class="aui-icon icon-warning">Icon</span>
                 <div class="message-content">



Mime
View raw message