You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by ka...@apache.org on 2007/10/01 09:45:31 UTC
svn commit: r580879 - in /webservices/rampart/tags/c/1.0.0-2:
rampart-bindist.sh xdocs/docs/installationguide.html
xdocs/docs/rampartc_manual.html
Author: kaushalye
Date: Mon Oct 1 00:45:30 2007
New Revision: 580879
URL: http://svn.apache.org/viewvc?rev=580879&view=rev
Log:
Updates
Modified:
webservices/rampart/tags/c/1.0.0-2/rampart-bindist.sh
webservices/rampart/tags/c/1.0.0-2/xdocs/docs/installationguide.html
webservices/rampart/tags/c/1.0.0-2/xdocs/docs/rampartc_manual.html
Modified: webservices/rampart/tags/c/1.0.0-2/rampart-bindist.sh
URL: http://svn.apache.org/viewvc/webservices/rampart/tags/c/1.0.0-2/rampart-bindist.sh?rev=580879&r1=580878&r2=580879&view=diff
==============================================================================
--- webservices/rampart/tags/c/1.0.0-2/rampart-bindist.sh (original)
+++ webservices/rampart/tags/c/1.0.0-2/rampart-bindist.sh Mon Oct 1 00:45:30 2007
@@ -57,9 +57,9 @@
cp -r $AXIS2C_HOME/modules/rampart $BIN_DIR/modules/
echo "Copy libraries"
-cp $AXIS2C_HOME/lib/liboxstokens.* $BIN_DIR/lib
-cp $AXIS2C_HOME/lib/libomxmlsec.* $BIN_DIR/lib
-cp $AXIS2C_HOME/lib/libomopenssl.* $BIN_DIR/lib
+cp -d $AXIS2C_HOME/lib/liboxstokens.* $BIN_DIR/lib
+cp -d $AXIS2C_HOME/lib/libomxmlsec.* $BIN_DIR/lib
+cp -d $AXIS2C_HOME/lib/libomopenssl.* $BIN_DIR/lib
echo "Copy samples"
#copy samples
Modified: webservices/rampart/tags/c/1.0.0-2/xdocs/docs/installationguide.html
URL: http://svn.apache.org/viewvc/webservices/rampart/tags/c/1.0.0-2/xdocs/docs/installationguide.html?rev=580879&r1=580878&r2=580879&view=diff
==============================================================================
--- webservices/rampart/tags/c/1.0.0-2/xdocs/docs/installationguide.html (original)
+++ webservices/rampart/tags/c/1.0.0-2/xdocs/docs/installationguide.html Mon Oct 1 00:45:30 2007
@@ -191,8 +191,8 @@
</ul>
<a id="src_run"></a>
-<h4><a id="engage"/></h4>
+<a id="engage"/>
<h2>Engage Rampart/C with axis2/C </h2>
<p>You can engage Rampart/C in global level or in service level.</p>
Modified: webservices/rampart/tags/c/1.0.0-2/xdocs/docs/rampartc_manual.html
URL: http://svn.apache.org/viewvc/webservices/rampart/tags/c/1.0.0-2/xdocs/docs/rampartc_manual.html?rev=580879&r1=580878&r2=580879&view=diff
==============================================================================
--- webservices/rampart/tags/c/1.0.0-2/xdocs/docs/rampartc_manual.html (original)
+++ webservices/rampart/tags/c/1.0.0-2/xdocs/docs/rampartc_manual.html Mon Oct 1 00:45:30 2007
@@ -77,17 +77,8 @@
<p>Rampart/C is configured using policy assertions defined in WS-Security
Policy specification 1.1. These policies are defined in policy.xml files.
-There are two policy files for a single Rampart configuration.</p>
-<ol>
- <li>incoming-secpolicy.xml</li>
- <li>outgoing-secpolicy.xml</li>
-</ol>
-The former defines how an outgoing message is secured, whilst the latter
-defines how the incoming message should be secured. Apart from the assertions
-mentioned in the specification, Rampart/C uses it's own assertions. (e.g. To
-specify keys and certificates). There are number of such sample policy files
-under rampart/samples/secpolicy.
-
+The client side policies are defined in a seperate policy.xml file located in the client's repository.
+The service's policies are defined in the services.xml file.
<h3>Rampart utilities</h3>