svn commit: r577539 - in /webservices/rampart/trunk/c: INSTALL NEWS

[ka...@apache.org]

Author: kaushalye
Date: Wed Sep 19 21:24:08 2007
New Revision: 577539

URL: http://svn.apache.org/viewvc?rev=577539&view=rev
Log:
Updating INSTALL and NEWS files

Modified:
    webservices/rampart/trunk/c/INSTALL
    webservices/rampart/trunk/c/NEWS

Modified: webservices/rampart/trunk/c/INSTALL
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/INSTALL?rev=577539&r1=577538&r2=577539&view=diff
==============================================================================
--- webservices/rampart/trunk/c/INSTALL (original)
+++ webservices/rampart/trunk/c/INSTALL Wed Sep 19 21:24:08 2007
@@ -14,7 +14,7 @@
 Build the source
 
 This can be done using the following command sequence:
-        ./configure --prefix=${AXIS2C_HOME} --enable-static=no --with-axis2=${AXIS2C_HOME}/include/axis2-1.0
+        ./configure --prefix=${AXIS2C_HOME} --enable-static=no --with-axis2=${AXIS2C_HOME}/include/axis2-1.1
         make
         make install
 
@@ -102,7 +102,7 @@
 	SET AXIS2C_HOME=[your-path-to-axis2c]
 
 2. Run the deploy_client_repo.bat file found in the samples\client\sec_echo folder.
-	This will create an axis2 client repository for the samples in the AXIS2C_HOME\clientrepo directory.
+	This will create an axis2 client repository for the samples in the AXIS2C_HOME\client_repo directory.
 
 To specify policies in the client side, please drop your policy.xml to the same directory as in axis2.xml
 To specify policies in the server side, please add policy assertions to the services.xml.

Modified: webservices/rampart/trunk/c/NEWS
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/NEWS?rev=577539&r1=577538&r2=577539&view=diff
==============================================================================
--- webservices/rampart/trunk/c/NEWS (original)
+++ webservices/rampart/trunk/c/NEWS Wed Sep 19 21:24:08 2007
@@ -9,15 +9,28 @@
     2. Digested password
 
 2. Ability to send Timestamp tokens
-3. Policy based configurations as per WS-Security Policy
-4. SOAP message encryption 
-5. SOAP message signature
+3. SOAP message encryption 
+4. SOAP message signature
+
+Major Changes Since Last Release
+--------------------------------
+1. WS-Security policy based configurations
+2. Replay detection support
+3. Improvements to the context model
+4. Authentication module implementation
+5. Credentials module implementation
+6. Impirovements to Key/Certificate loading mechanisms
+7. Easy to use deployment scripts 
+8. Memory leak fixes
+9. Many bug fixes
+
 
 Un-Implemented Architecture Features 
 ------------------------------------
 1. SAML support 
-2. WS Secure conversation
-3. WS Trust
+2. WS-Secure conversation
+3. WS-Trust
+4. WS-Security 1.1 support
 
 
 We welcome your early feedback on this implementation.