You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2012/12/14 19:48:00 UTC

svn commit: r842391 - in /websites/production/cxf/content: cache/docs.pageCache docs/ws-security.html

Author: buildbot
Date: Fri Dec 14 18:47:58 2012
New Revision: 842391

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/ws-security.html

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

Modified: websites/production/cxf/content/docs/ws-security.html
==============================================================================
--- websites/production/cxf/content/docs/ws-security.html (original)
+++ websites/production/cxf/content/docs/ws-security.html Fri Dec 14 18:47:58 2012
@@ -610,12 +610,11 @@ org.apache.ws.security.crypto.merlin.fil
 
 <p>Encryption involves the sender encrypting the message with the recipient's public key to ensure that only the recipient can read the message (only the recipient has its own private key, necessary for decrypting the message.)  This requires the sender to have the recipient's public key in its keystore.</p>
 
-<p>The process for encrypting is very similar to and indeed usually combined with the signature process above.  Our <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/security/">WS-Security test sample</a> provides an example of encrypting requests and responses, also check <a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/entry/cxf_x509_profile" rel="nofollow">this blog entry</a> for a more end-to-end example showing signature and encryption of both SOAP requests and responses.</p>
+<p>The process for encrypting is very similar to and indeed usually combined with the signature process above.  Our <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/security/">WS-Security test sample</a> (svn checkout <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/cxf/trunk/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/security/">http://svn.apache.org/repos/asf/cxf/trunk/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/security/</a>) provides an example of encrypting requests and responses, also check <a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/entry/cxf_x509_profile" rel="nofollow">this blog entry</a> for a more end-to-end example showing signature and encryption of both SOAP requests and responses.</p>
 
 <h1><a shape="rect" name="WS-Security-SecurityBestPractices"></a>Security Best Practices</h1>
 
-<p>Some guidelines are given at the WSS4J website about <a shape="rect" class="external-link" href="http://ws.apache.org/wss4j/best_practice.html">best practices</a> when using WS-Security. It is recommended to study the guidelines carefully.</p>
-</div>
+<p>Some guidelines are given at the WSS4J website about <a shape="rect" class="external-link" href="http://ws.apache.org/wss4j/best_practice.html">best practices</a> when using WS-Security. It is recommended to study the guidelines carefully.</p></div>
            </div>
            <!-- Content -->
          </td>