Author: buildbot
Date: Wed Aug  7 09:19:15 2013
New Revision: 873297

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-dataformat-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/xmlsecurity-dataformat.html

Modified: websites/production/camel/content/book-dataformat-appendix.html
==============================================================================
--- websites/production/camel/content/book-dataformat-appendix.html (original)
+++ websites/production/camel/content/book-dataformat-appendix.html Wed Aug  7 
09:19:15 2013
@@ -2851,7 +2851,7 @@ public class BindyComplexCsvUnmarshallTe
 
 <p>The XMLSecurity Data Format facilitates encryption and decryption of XML 
payloads at the Document, Element, and Element Content levels (including 
simultaneous multi-node encryption/decryption using XPath).</p>
 
-<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santaurio) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
+<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santuario) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
 
 <p><b>Available as of Camel 2.9</b><br clear="none">
 The XMLSecurity Data Format supports asymmetric key encryption. In this 
encryption model a symmetric key is generated and used to perform XML content 
encryption or decryption. This "content encryption key" is then itself 
encrypted using an asymmetric encryption algorithm that leverages the 
recipient's public key as the "key encryption key". Use of an asymmetric key 
encryption algorithm ensures that only the holder of the recipient's private 
key can access the generated symmetric encryption key. Thus, only the private 
key holder can decode the message. The XMLSecurity Data Format handles all of 
the logic required to encrypt and decrypt the message content and encryption 
key(s) using asymmetric key encryption.</p>
@@ -2955,7 +2955,7 @@ from("direct:start")
 ]]></script>
 </div></div>
 
-<h4><a shape="rect" 
name="BookDataFormatAppendix-PartialParyloadContentwithNamespacesupport"></a>Partial
 Paryload Content with Namespace support</h4>
+<h4><a shape="rect" 
name="BookDataFormatAppendix-PartialPayloadContentwithNamespacesupport"></a>Partial
 Payload Content with Namespace support</h4>
 <h5><a shape="rect" name="BookDataFormatAppendix-JavaDSL"></a>Java DSL</h5>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
 <script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Aug  7 09:19:15 
2013
@@ -14226,7 +14226,7 @@ public class BindyComplexCsvUnmarshallTe
 
 <p>The XMLSecurity Data Format facilitates encryption and decryption of XML 
payloads at the Document, Element, and Element Content levels (including 
simultaneous multi-node encryption/decryption using XPath).</p>
 
-<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santaurio) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
+<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santuario) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
 
 <p><b>Available as of Camel 2.9</b><br clear="none">
 The XMLSecurity Data Format supports asymmetric key encryption. In this 
encryption model a symmetric key is generated and used to perform XML content 
encryption or decryption. This "content encryption key" is then itself 
encrypted using an asymmetric encryption algorithm that leverages the 
recipient's public key as the "key encryption key". Use of an asymmetric key 
encryption algorithm ensures that only the holder of the recipient's private 
key can access the generated symmetric encryption key. Thus, only the private 
key holder can decode the message. The XMLSecurity Data Format handles all of 
the logic required to encrypt and decrypt the message content and encryption 
key(s) using asymmetric key encryption.</p>
@@ -14330,7 +14330,7 @@ from("direct:start")
 ]]></script>
 </div></div>
 
-<h4><a shape="rect" 
name="BookInOnePage-PartialParyloadContentwithNamespacesupport"></a>Partial 
Paryload Content with Namespace support</h4>
+<h4><a shape="rect" 
name="BookInOnePage-PartialPayloadContentwithNamespacesupport"></a>Partial 
Payload Content with Namespace support</h4>
 <h5><a shape="rect" name="BookInOnePage-JavaDSL"></a>Java DSL</h5>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
 <script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/xmlsecurity-dataformat.html
==============================================================================
--- websites/production/camel/content/xmlsecurity-dataformat.html (original)
+++ websites/production/camel/content/xmlsecurity-dataformat.html Wed Aug  7 
09:19:15 2013
@@ -89,7 +89,7 @@
 
 <p>The XMLSecurity Data Format facilitates encryption and decryption of XML 
payloads at the Document, Element, and Element Content levels (including 
simultaneous multi-node encryption/decryption using XPath).</p>
 
-<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santaurio) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
+<p>The encryption capability is based on formats supported using the Apache 
XML Security (Santuario) project. Symmetric encryption/decryption is currently 
supported using Triple-DES and AES (128, 192, and 256) encryption formats. 
Additional formats can be easily added later as needed. This capability allows 
Camel users to encrypt/decrypt payloads while being dispatched or received 
along a route.</p>
 
 <p><b>Available as of Camel 2.9</b><br clear="none">
 The XMLSecurity Data Format supports asymmetric key encryption. In this 
encryption model a symmetric key is generated and used to perform XML content 
encryption or decryption. This "content encryption key" is then itself 
encrypted using an asymmetric encryption algorithm that leverages the 
recipient's public key as the "key encryption key". Use of an asymmetric key 
encryption algorithm ensures that only the holder of the recipient's private 
key can access the generated symmetric encryption key. Thus, only the private 
key holder can decode the message. The XMLSecurity Data Format handles all of 
the logic required to encrypt and decrypt the message content and encryption 
key(s) using asymmetric key encryption.</p>
@@ -193,7 +193,7 @@ from("direct:start")
 ]]></script>
 </div></div>
 
-<h4><a shape="rect" 
name="XMLSecurityDataFormat-PartialParyloadContentwithNamespacesupport"></a>Partial
 Paryload Content with Namespace support</h4>
+<h4><a shape="rect" 
name="XMLSecurityDataFormat-PartialPayloadContentwithNamespacesupport"></a>Partial
 Payload Content with Namespace support</h4>
 <h5><a shape="rect" name="XMLSecurityDataFormat-JavaDSL"></a>Java DSL</h5>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
 <script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[


Reply via email to