You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by de...@apache.org on 2007/01/23 06:34:05 UTC

svn commit: r498925 [3/4] - in /webservices/axis2/trunk/java/xdocs: ./ 1_1/ 1_1/jibx/ download/1_1/ download/1_1_1/ modules/ modules/rampart/1_0/ modules/rampart/1_1/ modules/rampart/1_1/sec-conf/ modules/wss4j/0_94/0.94/ modules/wss4j/0_95/ modules/ws...

Modified: webservices/axis2/trunk/java/xdocs/index.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/index.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/index.html Mon Jan 22 21:34:03 2007
@@ -1,292 +1,284 @@
-<html>
-<head>
-  <meta http-equiv="content-type" content="">
-  <title>Apache Axis2/Java - Next Generation Web Services</title>
-  <link href="css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
-</head>
-
-<body lang="en">
-<h1>Welcome to Apache Axis2/Java</h1>
-
-<h2>13th November 2006 - Apache Axis2/Java Version 1.1 Released!</h2>
-
-<p>[ <a
-href="http://ws.apache.org/axis2/download.cgi"><strong>Download</strong></a>
-] | [ <a href="1_1/index.html"><strong>Documents Home</strong></a> ]</p>
-
-<p>Apache Axis2 is the core engine for Web services. It is a complete
-re-design and re-write of the widely used <a
-href="http://ws.apache.org/axis/">Apache Axis</a> SOAP stack to build on the
-lessons learnt from Apache Axis.</p>
-
-<h3><em>Apache Axis Project in a Nutshell:</em></h3>
-
-<p>Apache Axis is an implementation of the SOAP ("Simple Object Access
-Protocol") <a href="http://www.w3.org/TR/SOAP">submission</a> to W3C.</p>
-
-<p>Extract from the draft W3C specification:</p>
-
-<blockquote>
-  "SOAP is a lightweight protocol for exchanging structured information in a
-  decentralized, distributed environment. It is an XML based protocol that
-  consists of three parts: an envelope that defines a framework for
-  describing what is in a message and how to process it, a set of encoding
-  rules for expressing instances of application-defined datatypes, and a
-  convention for representing remote procedure calls and
-responses."</blockquote>
-
-<p>This project is a follow-on to the <a
-href="http://ws.apache.org/soap">Apache SOAP project</a>.</p>
-
-<p>Please see the <a href="http://ws.apache.org/axis/ref.html">Axis Reference
-Library</a> for a list of technical resources that should prove useful on
-this project.</p>
-
-<h3><em>Why Apache Axis2:</em></h3>
-
-<p>A new architecture for Axis was introduced during the August 2004 Summit
-in Colombo, Sri Lanka. This new architecture Axis2 is based on is more
-flexible, efficient and configurable in comparison to <a
-href="http://ws.apache.org/axis/java/architecture-guide.html">Axis1.x
-architecture</a>. Some well established concepts from Axis 1.x, like handlers
-etc., have been preserved in this new architecture.</p>
-
-<p>Apache Axis2 not only supports SOAP 1.1 and SOAP 1.2, but it also has
-integrated support for the widely popular <a
-href="http://www.xfront.com/REST-Web-Services.html">REST style of Web
-services</a>: the same business logic implementation can offer both a WS-*
-style interface as well as a REST style interface simultaneously.</p>
-
-<p>Apache Axis2 is more efficient, more modular and more XML-oriented than
-the older version. It is carefully designed to support the easy addition of
-plug-in "modules" that extend its functionality for features such as security
-and reliability. <a
-href="http://ws.apache.org/axis2/modules/index.html">Modules</a> currently
-available or under development include:</p>
-<ul>
-  <li><a
-    href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrm"
-    target="_blank">WS-ReliableMessaging</a> - Supported by <a
-    href="http://ws.apache.org/sandesha/sandesha2/">Apache Sandesha2</a></li>
-  <li><a
-    href="http://www-128.ibm.com/developerworks/library/specification/ws-tx/#coor"
-    target="_blank">WS-Coordination</a>  and <a
-    href="http://www-128.ibm.com/developerworks/library/specification/ws-tx/#atom"
-    target="_blank">WS-AtomicTransaction</a> - Supported by <a
-    href="http://ws.apache.org/kandula/">Apache Kandula2</a></li>
-  <li><a
-    href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss"
-    target="_blank">WS-Security</a> - Supported by <a
-    href="http://ws.apache.org/axis2/modules/index.html">Apache
-  Rampart</a></li>
-  <li><a href="http://www.w3.org/Submission/ws-addressing/"
-    target="_blank">WS-Addressing</a> -Module included as part of Axis2
-  core</li>
-</ul>
-
-<p>Apache Axis2 is built on <a
-href="http://ws.apache.org/commons/axiom/index.html">Apache AXIOM</a>, a high performant, pull-based XML object model.</p>
-
-<p>Axis2 comes with many new features, enhancements and industry
-specification implementations. The key features offered are as follows:</p>
-<ul>
-  <li><p style="margin-bottom: 0in"><strong>Speed</strong> - Axis2 uses its
-    own object model and StAX (Streaming API for XML) parsing to achieve
-    significantly greater speed than earlier versions of Apache Axis.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Low memory foot print</strong>-
-    Axis2 was designed ground-up keeping low memory foot print in mind.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>AXIOM</strong> - Axis2 comes with
-    its own light-weight object model, AXIOM, for message processing which is
-    extensible, highly performant and is developer convenient.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong><a name="Hot_Deployment"></a>Hot
-    Deployment</strong> - Axis2 is equipped with the capability of
-    deploying Web service &amp; handlers while the system is up and running.
-    In other words, new services can be added to the system without having to
-    shut down the server. Simply drop the required Web service archive into
-    the services directory in the repository and the deployment model will
-    automatically deploy the service and make it available for use.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Asynchronous Web
-    services</strong> - Axis2 now supports asynchronous Web services &amp;
-    asynchronous Web services invocation using non-blocking clients and
-    transports .</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>MEP Support</strong> - Axis2 now
-    comes handy with the flexibility to support Message Exchange Patterns
-    (MEPs) with in-built support for basic MEPs defined in WSDL 2.0.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Flexibility</strong> - The Axis2
-    architecture gives the developer complete freedom to insert extensions
-    into the engine for custom header processing, system management, and
-    <em>anything else you can imagine</em>.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Stability</strong> - Axis2
-    defines a set of published interfaces which change relatively slowly
-    compared to the rest of Axis.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Component-oriented
-    Deployment</strong> - You can easily define reusable networks of Handlers
-    to implement common patterns of processing for your applications, or to
-    distribute to partners.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Transport Framework</strong> - We
-    have a clean and simple abstraction for integrating and using Transports
-    (i.e., senders and listeners for SOAP over various protocols such as
-    SMTP, FTP, message-oriented middleware, etc), and the core of the engine
-    is completely transport-independent.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>WSDL support</strong> - Axis2
-    supports the Web Service Description Language, version <a
-    href="http://www.w3.org/TR/wsdl">1.1</a> and <a
-    href="http://www.w3.org/TR/wsdl20/">2.0</a>, which allows you to easily
-    build stubs to access remote services, and also to automatically export
-    machine-readable descriptions of your deployed services from Axis2.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Add-ons</strong> - Several Web
-    services specifications have been incorporated including <a
-    href="http://ws.apache.org/wss4j/" target="_blank">WSS4J</a> for security
-    (Apache Rampart), <a href="http://ws.apache.org/sandesha/"
-    target="_blank">Sandesha</a> for reliable messaging, <a
-    href="http://ws.apache.org/kandula/" target="_blank">Kandula</a> which is
-    an encapsulation of WS-Coordination, WS-AtomicTransaction and
-    WS-BusinessActivity.</p>
-  </li>
-  <li><p style="margin-bottom: 0in"><strong>Composition and
-    Extensibility</strong> - Modules and phases improve support for
-    composability and extensibility. Modules supports composability and is
-    able to add support for new WS-* specifications in a simple and clean
-    manner. They are however not <a href="#Hot_Deployment">hot deployable</a>
-    as they change the overall behavior of the system.</p>
-  </li>
-</ul>
-
-<p>We hope you enjoy using Axis2. Please note that this is an open-source
-effort. If you feel the code could use new features or fixes, or the
-documentation can be improved, please get involved and lend us a hand! The
-Axis developer community welcomes your participation.</p>
-
-<p>Let us know what you think! Send your feedback on Axis2 to "<a
-href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org</a>". Make sure
-to prefix the subject of the mail with [Axis2].</p>
-
-<h2>Features of Axis2 Latest Version</h2>
-
-<p>Apache Axis2 Version 1.1 comes to you with better Axis2 Databinding
-Framework (ADB) support, <a
-href="http://www.w3.org/TR/SOAP-attachments">attachments API</a>, Spring and
-complete support for SOAP with Attachments (SwA). Check out the complete
-features list below.</p>
-
-<h3>Programming Model</h3>
-<ul>
-  <li>Improved, XML-centric client API including full WSDL and policy
-  support</li>
-  <li>Support for any message exchange pattern</li>
-  <li>Synchronous and asynchronous calls</li>
-  <li>Archived service deployment model</li>
-  <li>Archived module deployment model supporting controlled extensibility
-    with versioning support</li>
-  <li><a href="#Hot_Deployment">Hot deployment</a></li>
-  <li>WS-Policy driven code generation extensions</li>
-  <li>Flexible service life cycle model</li>
-  <li>Support for querying service's WSDL (using ?wsdl), schema (using ?xsd)
-    and policies (using ?policy)</li>
-</ul>
-
-<h3>Supported Specifications</h3>
-<ul>
-  <li>SOAP 1.1 and 1.2</li>
-  <li>Message Transmission Optimization Mechanism (MTOM), XML Optimized
-    Packaging (XOP) and SOAP with Attachments</li>
-  <li>WSDL 1.1, including both SOAP and HTTP bindings</li>
-  <li>WS-Addressing (submission and final)</li>
-  <li>WS-Policy</li>
-  <li>SAAJ 1.1</li>
-</ul>
-
-<h3>Transports</h3>
-<ul>
-  <li>HTTP</li>
-  <li>SMTP</li>
-  <li>JMS</li>
-  <li>TCP</li>
-</ul>
-
-<h3>Supported Data Bindings</h3>
-<ul>
-  <li>Axis Data Binding (ADB)</li>
-  <li>XMLBeans</li>
-  <li>JibX</li>
-  <li>JaxMe</li>
-</ul>
-
-<h2><a name="Tools_included_in this_Release">Tools Included In This
-Release</a></h2>
-
-<p>[<a href="http://ws.apache.org/axis2/tools/index.html"
-target="_blank">Download Tool Plug-ins</a>]</p>
-<ol type="1">
-  <li>Axis2 Web Application (Web App)</li>
-  <li>WSDL2WS- <a href="tools/1_1/eclipse/wsdl2java-plugin.html"
-    target="_blank">eclipse plug-in</a><a>/</a> <a
-    href="tools/1_1/CodegenToolReference.html" target="_blank">Command
-    line version</a><a>/</a><a
-    href="tools/1_1/idea/Idea_plug-in_userguide.html#WSDL2Java_Code_Generation"
-    target="_blank">IntelliJ IDEA plug-in</a><a>/</a><a
-    href="tools/1_1/maven-plugins/maven-wsdl2code-plugin.html"
-    target="_blank">Maven2 WSDL2Code Plug-in</a></li>
-  <li>Service Archive Wizard- <a
-    href="tools/1_1/eclipse/servicearchiver-plugin.html"
-    target="_blank">eclipse plug-in</a>/ <a
-    href="tools/1_1/idea/Idea_plug-in_userguide.html#Create_Service_Archive"
-    target="_blank">IntelliJ IDEA plug-in</a>/ <a
-    href="tools/1_1/maven-plugins/maven-aar-plugin.html"
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>Apache Axis2/Java - Next Generation Web Services</title>
+  <link href="css/axis-docs.css" rel="stylesheet" type="text/css" media="all">
+</head>
+
+<body lang="en">
+<h1>Welcome to Apache Axis2/Java</h1>
+
+<h2>09th January 2006 - Apache Axis2/Java Version 1.1.1 Released!</h2>
+
+<p>[ <a
+href="http://ws.apache.org/axis2/download.cgi"><strong>Download</strong></a>
+] | [ <a href="1_1/index.html"><strong>Documents Home</strong></a> ]</p>
+
+<p>Apache Axis2 is the core engine for Web services. It is a complete
+re-design and re-write of the widely used <a
+href="http://ws.apache.org/axis/">Apache Axis</a> SOAP stack to build on the
+lessons learnt from Apache Axis.</p>
+
+<h3><em>Apache Axis Project in a Nutshell:</em></h3>
+
+<p>Apache Axis is an implementation of the SOAP ("Simple Object Access
+Protocol") <a href="http://www.w3.org/TR/SOAP">submission</a> to W3C.</p>
+
+<p>Extract from the draft W3C specification:</p>
+
+<blockquote>
+  "SOAP is a lightweight protocol for exchanging structured information in a
+  decentralized, distributed environment. It is an XML based protocol that
+  consists of three parts: an envelope that defines a framework for
+  describing what is in a message and how to process it, a set of encoding
+  rules for expressing instances of application-defined datatypes, and a
+  convention for representing remote procedure calls and
+responses."</blockquote>
+
+<p>This project is a follow-on to the <a
+href="http://ws.apache.org/soap">Apache SOAP project</a>.</p>
+
+<p>Please see the <a href="http://ws.apache.org/axis/ref.html">Axis Reference
+Library</a> for a list of technical resources that should prove useful on
+this project.</p>
+
+<h3><em>Why Apache Axis2:</em></h3>
+
+<p>A new architecture for Axis was introduced during the August 2004 Summit
+in Colombo, Sri Lanka. This new architecture Axis2 is based on is more
+flexible, efficient and configurable in comparison to <a
+href="http://ws.apache.org/axis/java/architecture-guide.html">Axis1.x
+architecture</a>. Some well established concepts from Axis 1.x, like handlers
+etc., have been preserved in this new architecture.</p>
+
+<p>Apache Axis2 not only supports SOAP 1.1 and SOAP 1.2, but it also has
+integrated support for the widely popular <a
+href="http://www.xfront.com/REST-Web-Services.html">REST style of Web
+services</a>: the same business logic implementation can offer both a WS-*
+style interface as well as a REST style interface simultaneously.</p>
+
+<p>Apache Axis2 is more efficient, more modular and more XML-oriented than
+the older version. It is carefully designed to support the easy addition of
+plug-in "modules" that extend its functionality for features such as security
+and reliability. <a
+href="http://ws.apache.org/axis2/modules/index.html">Modules</a> currently
+available or under development include:</p>
+<ul>
+  <li><a
+    href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrm"
+    target="_blank">WS-ReliableMessaging</a> - Supported by <a
+    href="http://ws.apache.org/sandesha/sandesha2/">Apache Sandesha2</a></li>
+  <li><a
+    href="http://www-128.ibm.com/developerworks/library/specification/ws-tx/#coor"
+    target="_blank">WS-Coordination</a>  and <a
+    href="http://www-128.ibm.com/developerworks/library/specification/ws-tx/#atom"
+    target="_blank">WS-AtomicTransaction</a> - Supported by <a
+    href="http://ws.apache.org/kandula/">Apache Kandula2</a></li>
+  <li><a
+    href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss"
+    target="_blank">WS-Security</a> - Supported by <a
+    href="http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html">Apache
+  Rampart</a></li>
+  <li><a href="http://www.w3.org/Submission/ws-addressing/"
+    target="_blank">WS-Addressing</a> -Module included as part of Axis2
+  core</li>
+</ul>
+
+<p>Apache Axis2 is built on <a
+href="http://ws.apache.org/commons/axiom/index.html">Apache AXIOM</a>, a new
+high performant, pull-based XML object model that was released two days
+ago.</p>
+
+<p>Axis2 comes with many new features, enhancements and industry
+specification implementations. The key features offered are as follows:</p>
+<ul>
+  <li><p style="margin-bottom: 0in"><strong>Speed</strong> - Axis2 uses its
+    own object model and StAX (Streaming API for XML) parsing to achieve
+    significantly greater speed than earlier versions of Apache Axis.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Low memory foot print</strong>-
+    Axis2 was designed ground-up keeping low memory foot print in mind.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>AXIOM</strong> - Axis2 comes with
+    its own light-weight object model, AXIOM, for message processing which is
+    extensible, highly performant and is developer convenient.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong><a name="Hot_Deployment"></a>Hot
+    Deployment</strong> - Axis2 is equipped with the capability of deploying
+    Web service &amp; handlers while the system is up and running. In other
+    words, new services can be added to the system without having to shut
+    down the server. Simply drop the required Web service archive into the
+    services directory in the repository and the deployment model will
+    automatically deploy the service and make it available for use.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Asynchronous Web
+    services</strong> - Axis2 now supports asynchronous Web services &amp;
+    asynchronous Web services invocation using non-blocking clients and
+    transports .</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>MEP Support</strong> - Axis2 now
+    comes handy with the flexibility to support Message Exchange Patterns
+    (MEPs) with in-built support for basic MEPs defined in WSDL 2.0.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Flexibility</strong> - The Axis2
+    architecture gives the developer complete freedom to insert extensions
+    into the engine for custom header processing, system management, and
+    <em>anything else you can imagine</em>.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Stability</strong> - Axis2
+    defines a set of published interfaces which change relatively slowly
+    compared to the rest of Axis.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Component-oriented
+    Deployment</strong> - You can easily define reusable networks of Handlers
+    to implement common patterns of processing for your applications, or to
+    distribute to partners.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Transport Framework</strong> - We
+    have a clean and simple abstraction for integrating and using Transports
+    (i.e., senders and listeners for SOAP over various protocols such as
+    SMTP, FTP, message-oriented middleware, etc), and the core of the engine
+    is completely transport-independent.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>WSDL support</strong> - Axis2
+    supports the Web Service Description Language, version <a
+    href="http://www.w3.org/TR/wsdl">1.1</a> and <a
+    href="http://www.w3.org/TR/wsdl20/">2.0</a>, which allows you to easily
+    build stubs to access remote services, and also to automatically export
+    machine-readable descriptions of your deployed services from Axis2.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Add-ons</strong> - Several Web
+    services specifications have been incorporated including <a
+    href="http://ws.apache.org/wss4j/" target="_blank">WSS4J</a> for security
+    (Apache Rampart), <a href="http://ws.apache.org/sandesha/"
+    target="_blank">Sandesha</a> for reliable messaging, <a
+    href="http://ws.apache.org/kandula/" target="_blank">Kandula</a> which is
+    an encapsulation of WS-Coordination, WS-AtomicTransaction and
+    WS-BusinessActivity.</p>
+  </li>
+  <li><p style="margin-bottom: 0in"><strong>Composition and
+    Extensibility</strong> - Modules and phases improve support for
+    composability and extensibility. Modules supports composability and is
+    able to add support for new WS-* specifications in a simple and clean
+    manner. They are however not <a href="#Hot_Deployment">hot deployable</a>
+    as they change the overall behavior of the system.</p>
+  </li>
+</ul>
+
+<p>We hope you enjoy using Axis2. Please note that this is an open-source
+effort. If you feel the code could use new features or fixes, or the
+documentation can be improved, please get involved and lend us a hand! The
+Axis developer community welcomes your participation.</p>
+
+<p>Let us know what you think! Send your feedback on Axis2 to "<a
+href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org</a>". Make sure
+to prefix the subject of the mail with [Axis2].</p>
+
+<h2>Features of Axis2 Latest Version</h2>
+
+<p>Apache Axis2 Version 1.1.1 comes to you with performance improvements and
+bug fixes over the 1.1 release. Check out the complete features list
+below.</p>
+
+<h3>Programming Model</h3>
+<ul>
+  <li>Improved, XML-centric client API including full WSDL and policy
+  support</li>
+  <li>Support for any message exchange pattern</li>
+  <li>Synchronous and asynchronous calls</li>
+  <li>Archived service deployment model</li>
+  <li>Archived module deployment model supporting controlled extensibility
+    with versioning support</li>
+  <li><a href="#Hot_Deployment">Hot deployment</a></li>
+  <li>WS-Policy driven code generation extensions</li>
+  <li>Flexible service life cycle model</li>
+  <li>Support for querying service's WSDL (using ?wsdl), schema (using ?xsd)
+    and policies (using ?policy)</li>
+</ul>
+
+<h3>Supported Specifications</h3>
+<ul>
+  <li>SOAP 1.1 and 1.2</li>
+  <li>Message Transmission Optimization Mechanism (MTOM), XML Optimized
+    Packaging (XOP) and SOAP with Attachments</li>
+  <li>WSDL 1.1, including both SOAP and HTTP bindings</li>
+  <li>WS-Addressing (submission and final)</li>
+  <li>WS-Policy</li>
+  <li>SAAJ 1.1</li>
+</ul>
+
+<h3>Transports</h3>
+<ul>
+  <li>HTTP</li>
+  <li>SMTP</li>
+  <li>JMS</li>
+  <li>TCP</li>
+</ul>
+
+<h3>Supported Data Bindings</h3>
+<ul>
+  <li>Axis Data Binding (ADB)</li>
+  <li>XMLBeans</li>
+  <li>JibX</li>
+  <li>JaxMe</li>
+</ul>
+
+<h2><a name="Tools_included_in this_Release">Tools Included In This
+Release</a></h2>
+
+<p>[<a href="http://ws.apache.org/axis2/tools/index.html"
+target="_blank">Download Tool Plug-ins</a>]</p>
+<ol type="1">
+  <li>Axis2 Web Application (Web App)</li>
+  <li>WSDL2WS- <a href="tools/1_1/eclipse/wsdl2java-plugin.html"
+    target="_blank">eclipse plug-in</a><a>/</a> <a
+    href="tools/1_1/CodegenToolReference.html" target="_blank">Command line
+    version</a><a>/</a><a
+    href="tools/1_1/idea/Idea_plug-in_userguide.html#WSDL2Java_Code_Generation"
+    target="_blank">IntelliJ IDEA plug-in</a><a>/</a><a
+    href="tools/1_1/maven-plugins/maven-wsdl2code-plugin.html"
+    target="_blank">Maven2 WSDL2Code Plug-in</a></li>
+  <li>Service Archive Wizard- <a
+    href="tools/1_1/eclipse/servicearchiver-plugin.html"
+    target="_blank">eclipse plug-in</a>/ <a
+    href="tools/1_1/idea/Idea_plug-in_userguide.html#Create_Service_Archive"
+    target="_blank">IntelliJ IDEA plug-in</a>/ <a
+    href="tools/1_1/maven-plugins/maven-aar-plugin.html"
     target="_blank">Maven2 AAR Plug-in</a></li>
-  <li>Java2WSDL- <a href="tools/1_1/maven-plugins/maven-java2wsdl-plugin.html"
-    target="_blank">Maven2 Java2WSDL Plug-in</a>
-    </li>
-</ol>
-
-<h2>Extension Modules</h2>
-<ul>
-  <li>Apache Rampart: Supporting WS-Security (and soon WS-Policy)</li>
-  <li>Apache Sandesha2: Supporting WS-Reliable Messaging</li>
-</ul>
-(Apache Axis2 comes built in with a module that supports WS-Addressing.)
-
-<h2>Known Issues and Limitations</h2>
-<ul>
-  <li>JaxMe and JAXBRI data binding support is experimental</li>
-  <li>AXIS2-595: Hot re-deployment in Apache Tomcat has problems</li>
-  <li>Axis Data Binding (ADB) does not support the following construct(s):
-    <ol>
-      <li>AXIS2-983: Support for Simple Type Union and Simple Type List</li>
-      <li>AXIS2-1092: Support for xs:list inside an xs:simpleType</li>
-      <li>AXIS2-1093: Support for xs:union inside xs:simpleType</li>
-    </ol>
-  </li>
-  <li>No support yet for unwrapping of doc/lit WSDL files (in stub
-  generation)</li>
-  <li>No support yet for rpc/encoded style WSDL documents (in stub
-  generation)</li>
-   <li>Idea plugin shows random behavior when XMLBeans is used</li>
-</ul>
-
-<h2>Archived News</h2>
-
-<p>For information on previous Axis2 releases running up to the current
-release see <a href="archived_news.html" target="_blank">'Axis2 Archived
-News'</a> page.</p>
-For other news items from Apache Software Foundation see:
-<ul>
-  <li><a
-    href="http://www.apachenews.org/archives/cat_apache_webservices_index.html">Web
-    services related news on the Apache News Blog Online</a></li>
-  <li><a href="http://www.apachenews.org/">The Apache News Blog
-  Online</a></li>
-</ul>
-</body>
-</html>
+  <li>Java2WSDL- <a
+    href="tools/1_1/maven-plugins/maven-java2wsdl-plugin.html"
+    target="_blank">Maven2 Java2WSDL Plug-in</a></li>
+</ol>
+
+<h2>Extension Modules</h2>
+<ul>
+  <li>Apache Rampart: Supporting WS-Security (and soon WS-Policy)</li>
+  <li>Apache Sandesha2: Supporting WS-Reliable Messaging</li>
+</ul>
+(Apache Axis2 comes built in with a module that supports WS-Addressing.)
+
+<h2>Known Issues and Limitations</h2>
+<ul>
+   <li>ADB does not support unwrapping of response messages(coming in 1.2)</li>
+   <li>JSR 181/183 Annotation support (coming in 1.2)</li>
+   <li>JaxMe and JAXBRI data binding support is experimental</li>
+   <li>Simple Axis Server does not support POX/REST</li>
+   <li>RPC  Message Receiver does not validate request against the schema (AXIS2-1943)</li>
+   <li>Axis2 Idea plugin shows random behavior when XMLBeans is used</li>
+</ul>
+
+<h2>Archived News</h2>
+
+<p>For information on previous Axis2 releases running up to the current
+release see <a href="archived_news.html" target="_blank">'Axis2 Archived
+News'</a> page.</p>
+For other news items from Apache Software Foundation see:
+<ul>
+  <li><a
+    href="http://www.apachenews.org/archives/cat_apache_webservices_index.html">Web
+    services related news on the Apache News Blog Online</a></li>
+  <li><a href="http://www.apachenews.org/">The Apache News Blog
+  Online</a></li>
+</ul>
+</body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/modules/index.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/index.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/index.html Mon Jan 22 21:34:03 2007
@@ -1,103 +1,148 @@
-<html>
-<head>
-  <meta http-equiv="content-type" content="">
-  <title>:: Axis2 Modules ::</title>
-  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
-</head>
-
-<body lang="en">
-<h1>Apache Axis2 Modules</h1>
-
-<p>Axis2 architecture is flexible enough to extend its functionalities using
-modules. This page is maintained to keep track of the relevant modules that
-are developed on top of Axis2.</p>
-
-<table width="675" border="1" align="center" cellpadding="1">
-  <tbody>
-    <tr>
-      <th width="68" scope="col">Name</th>
-      <th width="147" scope="col">Description</th>
-      <th width="52" scope="col">Version</th>
-      <th width="80" scope="col">Compatible Axis2 version</th>
-      <th width="97" scope="col">Downloads</th>
-      <th width="191" scope="col">Comments</th>
-    </tr>
-    <tr>
-      <td><a href="addressing/index.html">Addressing</a></td>
-      <td>This is an implementation of WS-Addressing submission version
-        (2004-08) and WS-Addressing 2005-08 versions.</td>
-      <td>1.1</td>
-      <td>1.1</td>
-      <td><a
-        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar"
-        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar">mar</a>
-        <a
-        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.md5"
-        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.md5">MD5</a>
-        <a
-        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.asc"
-        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.asc">PGP</a></td>
-      <td></td>
-    </tr>
-   
-   <tr>
-    <td><a
-    href="../1_1/soapmonitor-module.html">SOAP Monitor</a></td>
-    <td>SOAP Monitor utility provides a way for Web services developers to monitor the SOAP messages being sent/received without requiring any special configuration or restarting of the server</td>
-    <td>1.1</td>
-    <td>1.1</td>
-    <td><a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip">zip</a>
-    <a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.md5"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.md5">MD5</a>
-    <a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.asc"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.asc">PGP</a>  </td>
-    <td></td>
-    </tr>
-
-    <tr>
-    <td><a
-    href="http://ws.apache.org/sandesha/sandesha2/index.html">Sandesha2</a></td>
-    <td>An implementation of WS-RM specification February 2005</td>
-    <td>1.1</td>
-    <td>1.1</td>
-    <td><a
-    href="http://apache.hoxt.com/ws/sandesha2/1_1/sandesha2-1.1-src.zip"
-    title="http://apache.hoxt.com/ws/sandesha2/1_1/sandesha2-1.1-src.zip">zip</a>
-    <a
-    href="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.md5"
-    title="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.md5">MD5</a>
-    <a
-    href="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.asc"
-    title="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.asc">PGP</a></td>
-    <td>Click <a
-    href="http://people.apache.org/repo/m1-snapshot-repository/org.apache.sandesha2/">here</a> to get
-    the Sandesha2 nightly builds compatible with the latest Axis2
-    SNAPSHOT.</td>
-    </tr>
-    <tr>
-    <td><a href="rampart/1_1/security-module.html">Rampart</a></td>
-    <td>The WS-Security and WS-SecureConversation implementation for axis2. Now with a new configuration model based on WS-SecurityPolicy</td>
-    <td>1.1</td>
-    <td>1.1</td>
-    <td><a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip">Distro zip</a>
-    <a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.md5"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.md5">MD5</a>
-    <a
-    href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.asc"
-    title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.asc">PGP</a></td>
-    <td>Please follow the instructions in the README.txt available in the rampart-1.1.zip file to copy the required libraries to the main "lib" dir of Axis2</td>
-    </tr>
-  </tbody>
-</table>
-<br>
-Previous module releases are available <a href="previous.html">here</a>
-
-</body>
-</html>
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>:: Axis2 Modules ::</title>
+  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css"
+  media="all">
+</head>
+
+<body lang="en">
+<h1>Apache Axis2 Modules</h1>
+
+<p>Axis2 architecture is flexible enough to extend its functionalities using
+modules. This page is maintained to keep track of the relevant modules that
+are developed on top of Axis2.</p>
+
+<table width="675" border="1" align="center" cellpadding="1">
+  <tbody>
+    <tr>
+      <th width="68" scope="col">Name</th>
+      <th width="147" scope="col">Description</th>
+      <th width="52" scope="col">Version</th>
+      <th width="80" scope="col">Compatible Axis2 version</th>
+      <th width="97" scope="col">Downloads</th>
+      <th width="191" scope="col">Comments</th>
+    </tr>
+    <tr>
+      <td><a href="addressing/index.html">Addressing</a></td>
+      <td>This is an implementation of WS-Addressing submission version
+        (2004-08) and WS-Addressing 2005-08 versions.</td>
+      <td>1.1.1</td>
+      <td>1.1.1</td>
+      <td><a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar">mar</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar.md5"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar.asc"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/addressing-1.1.1.mar.asc">PGP</a></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td><a href="../1_1/soapmonitor-module.html">SOAP Monitor</a></td>
+      <td>SOAP Monitor utility provides a way for Web services developers to
+        monitor the SOAP messages being sent/received without requiring any
+        special configuration or restarting of the server</td>
+      <td>1.1.1</td>
+      <td>1.1.1</td>
+      <td><a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip">zip</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip.md5"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip.asc"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1_1/soapmonitor-1.1.1.zip.asc">PGP</a></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td><a href="addressing/index.html">Addressing</a></td>
+      <td>This is an implementation of WS-Addressing submission version
+        (2004-08) and WS-Addressing 2005-08 versions.</td>
+      <td>1.1</td>
+      <td>1.1</td>
+      <td><a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar">mar</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.md5"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.asc"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/addressing-1.1.mar.asc">PGP</a></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td><a href="../1_1/soapmonitor-module.html">SOAP Monitor</a></td>
+      <td>SOAP Monitor utility provides a way for Web services developers to
+        monitor the SOAP messages being sent/received without requiring any
+        special configuration or restarting of the server</td>
+      <td>1.1</td>
+      <td>1.1</td>
+      <td><a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip">zip</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.md5"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.asc"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip.asc">PGP</a></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td><a
+        href="http://ws.apache.org/sandesha/sandesha2/index.html">Sandesha2</a></td>
+      <td>An implementation of WS-RM specification February 2005</td>
+      <td>1.1</td>
+      <td>1.1, 1.1.1</td>
+      <td><a
+        href="http://apache.hoxt.com/ws/sandesha2/1_1/sandesha2-1.1-src.zip"
+        title="http://apache.hoxt.com/ws/sandesha2/1_1/sandesha2-1.1-src.zip">zip</a>
+        <a
+        href="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.md5"
+        title="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.asc"
+        title="http://www.apache.org/dist/ws/sandesha2/1_1/sandesha2-1.1-src.zip.asc">PGP</a></td>
+      <td>Click <a
+        href="http://people.apache.org/repo/m1-snapshot-repository/org.apache.sandesha2/">here</a>
+        to get the Sandesha2 nightly builds compatible with the latest Axis2
+        SNAPSHOT.</td>
+    </tr>
+    <tr>
+      <td><a href="rampart/1_1/security-module.html">Rampart</a></td>
+      <td>The WS-Security and WS-SecureConversation implementation for axis2.
+        Now with a new configuration model based on WS-SecurityPolicy</td>
+      <td>1.1</td>
+      <td>1.1, 1.1.1</td>
+      <td><a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip">Distro
+        zip</a> <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.md5"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.md5">MD5</a>
+        <a
+        href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.asc"
+        title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip.asc">PGP</a></td>
+      <td>Please follow the instructions in the README.txt available in the
+        rampart-1.1.zip file to copy the required libraries to the main "lib"
+        dir of Axis2.
+
+        <p></p>
+
+        <p><strong>Note</strong>: In Axis2 v1.1.1 to run Rampart v1.1
+        samples, change the addressing mar value to adressing-1.1.1.mar as
+        given below; <code>&lt;property name="addressing.mar"
+        value="addressing-1.1.1.mar"/&gt;</code> in
+        ..\rampart-1.1\samples\basic\build.xml</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<br>
+Previous module releases are available <a href="previous.html">here</a></body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/modules/previous.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/previous.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/previous.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/previous.html Mon Jan 22 21:34:03 2007
@@ -33,7 +33,7 @@
         <a
         href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_0/addressing-1.0.mar.asc"
         title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_0/addressing-1.0.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
     <tr>
       <td><a href="rampart/1_0/security-module.html">Rampart</a></td>
@@ -52,7 +52,7 @@
         <a
         href="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/rampart/1_0/rampart-1.0.mar.asc"
         title="http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/rampart/1_0/rampart-1.0.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
     <tr>
       <td><a
@@ -89,7 +89,7 @@
         <a
         href="http://archive.apache.org/dist/ws/axis2/modules/addressing/0_95/addressing-0.95.mar.asc"
         title="http://archive.apache.org/dist/ws/axis2/modules/addressing/0_95/addressing-0.95.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
     <tr>
       <td><a href="http://ws.apache.org/axis2/modules/wss4j/0_95/security-module.html">security</a></td>
@@ -106,7 +106,7 @@
         <a
         href="http://archive.apache.org/dist/ws/axis2/modules/wss4j/0_95/security-0.95.mar.asc"
         title="http://archive.apache.org/dist/ws/axis2/modules/wss4j/0_95/security-0.95.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
     <tr>
       <td><a
@@ -145,11 +145,11 @@
         <a
         href="http://archive.apache.org/dist/ws/axis2/modules/addressing/0_94/addressing-0.94.mar.asc"
         title="http://archive.apache.org/dist/ws/axis2/modules/addressing/0_94/addressing-0.94.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
     <tr>
       <td><a href="http://ws.apache.org/axis2/modules/wss4j/0_94/0.94/security-module.html">security</a></td>
-      <td> </td>
+      <td></td>
       <td>0.94</td>
       <td>0.94</td>
       <td><a
@@ -161,7 +161,7 @@
         <a
         href="http://archive.apache.org/dist/ws/axis2/modules/wss4j/0_94/security-0.94.mar.asc"
         title="http://archive.apache.org/dist/ws/axis2/modules/wss4j/0_94/security-0.94.mar.asc">PGP</a></td>
-      <td> </td>
+      <td></td>
     </tr>
   </tbody>
 </table>

Modified: webservices/axis2/trunk/java/xdocs/modules/rampart/1_0/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/rampart/1_0/security-module.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/rampart/1_0/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/rampart/1_0/security-module.html Mon Jan 22 21:34:03 2007
@@ -2,17 +2,18 @@
 <html>
 <head>
   <meta http-equiv="content-type" content="">
+  <link href="../../../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
   <title>Rampart : WS-Security module for Axis2</title>
 </head>
 
 <body>
-<h1>Securing SOAP Messages with WSS4J</h1>
+<h1>Securing SOAP Messages with Rampart</h1>
 
 <p><em>-For Axis2 Version 1.0</em></p>
 
-<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security
-features, called "rampart". This document explains how to engage and
-configure rampart module.</p>
+<p>Axis2 comes with a module based on Apache WSS4J [1] to provide WS-Security
+features, called "Rampart". This document explains how to engage and
+configure Rampart module.</p>
 
 <h2>Content</h2>
 <ul>

Added: webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/rampart-config.xsd
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/rampart-config.xsd?view=auto&rev=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/rampart-config.xsd (added)
+++ webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/rampart-config.xsd Mon Jan 22 21:34:03 2007
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ramp="http://ws.apache.org/rampart/policy" targetNamespace="http://ws.apache.org/rampart/policy" elementFormDefault="qualified" attributeFormDefault="unqualified">
+	<xs:element name="RampartConfig">
+		<xs:annotation>
+			<xs:documentation>Rampart specific configuration assertion</xs:documentation>
+		</xs:annotation>
+		<xs:complexType>
+			<xs:sequence>
+				<xs:element name="user" type="xs:string"/>
+				<xs:element name="encryptionUser" type="xs:string" minOccurs="0"/>
+				<xs:element name="passwordCallbackClass" type="xs:string"/>
+				<xs:element name="encryptionCypto" type="ramp:crypto" minOccurs="0"/>
+				<xs:element name="signatureCypto" type="ramp:crypto" minOccurs="0"/>
+			</xs:sequence>
+		</xs:complexType>
+	</xs:element>
+	<xs:complexType name="crypto">
+		<xs:annotation>
+			<xs:documentation>Crypto configuration assertion</xs:documentation>
+		</xs:annotation>
+		<xs:sequence maxOccurs="unbounded">
+			<xs:element name="property" type="xs:string"/>
+		</xs:sequence>
+		<xs:attribute name="provider"/>
+	</xs:complexType>
+</xs:schema>

Added: webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-policy.xml
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-policy.xml?view=auto&rev=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-policy.xml (added)
+++ webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-policy.xml Mon Jan 22 21:34:03 2007
@@ -0,0 +1,89 @@
+<!--
+  ~ Copyright 2004,2005 The Apache Software Foundation.
+  ~
+  ~  Licensed under the Apache License, Version 2.0 (the "License");
+  ~  you may not use this file except in compliance with the License.
+  ~  You may obtain a copy of the License at
+  ~
+  ~       http://www.apache.org/licenses/LICENSE-2.0
+  ~
+  ~  Unless required by applicable law or agreed to in writing, software
+  ~  distributed under the License is distributed on an "AS IS" BASIS,
+  ~  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  ~  See the License for the specific language governing permissions and
+  ~  limitations under the License.
+  -->
+<wsp:Policy wsu:Id="SigEncrTripleDesRSA15DK" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
+<wsp:ExactlyOne>
+	<wsp:All>
+		<sp:AsymmetricBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+			<wsp:Policy>
+				<sp:InitiatorToken>
+					<wsp:Policy>
+						<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
+							<wsp:Policy>
+								<sp:RequireDerivedKeys/>
+								<sp:WssX509V3Token10/>
+							</wsp:Policy>
+						</sp:X509Token>
+					</wsp:Policy>
+				</sp:InitiatorToken>
+				<sp:RecipientToken>
+					<wsp:Policy>
+						<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
+							<wsp:Policy>
+								<sp:RequireDerivedKeys/>
+								<sp:WssX509V3Token10/>
+							</wsp:Policy>
+						</sp:X509Token>
+					</wsp:Policy>
+				</sp:RecipientToken>
+				<sp:AlgorithmSuite>
+					<wsp:Policy>
+						<sp:TripleDesRsa15/>
+					</wsp:Policy>
+				</sp:AlgorithmSuite>
+				<sp:Layout>
+					<wsp:Policy>
+						<sp:Strict/>
+					</wsp:Policy>
+				</sp:Layout>
+				<sp:IncludeTimestamp/>
+				<sp:OnlySignEntireHeadersAndBody/>
+			</wsp:Policy>
+		</sp:AsymmetricBinding>
+		<sp:Wss10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+			<wsp:Policy>
+				<sp:MustSupportRefKeyIdentifier/>
+				<sp:MustSupportRefIssuerSerial/>
+			</wsp:Policy>
+		</sp:Wss10>
+		<sp:SignedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+			<sp:Body/>
+		</sp:SignedParts>
+		<sp:EncryptedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+			<sp:Body/>
+		</sp:EncryptedParts>
+		<ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy"> 
+			<ramp:user>alice</ramp:user>
+			<ramp:encryptionUser>bob</ramp:encryptionUser>
+			<ramp:passwordCallbackClass>org.apache.rampart.PWCallback</ramp:passwordCallbackClass>
+			
+			<ramp:signatureCrypto>
+				<ramp:crypto provider="org.apache.ws.security.components.crypto.Merlin">
+					<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property>
+					<ramp:property name="org.apache.ws.security.crypto.merlin.file">test-resources/rampart/store.jks</ramp:property>
+					<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.password">password</ramp:property>
+				</ramp:crypto>
+			</ramp:signatureCrypto>
+			<ramp:encryptionCypto>
+				<ramp:crypto provider="org.apache.ws.security.components.crypto.Merlin">
+					<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property>
+					<ramp:property name="org.apache.ws.security.crypto.merlin.file">test-resources/rampart/store.jks</ramp:property>
+					<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.password">password</ramp:property>
+				</ramp:crypto>
+			</ramp:encryptionCypto>
+		</ramp:RampartConfig>
+	</wsp:All>
+</wsp:ExactlyOne>
+</wsp:Policy>

Added: webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-services.xml
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-services.xml?view=auto&rev=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-services.xml (added)
+++ webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-services.xml Mon Jan 22 21:34:03 2007
@@ -0,0 +1,104 @@
+<!--
+  ~ Copyright 2004,2005 The Apache Software Foundation.
+  ~
+  ~  Licensed under the Apache License, Version 2.0 (the "License");
+  ~  you may not use this file except in compliance with the License.
+  ~  You may obtain a copy of the License at
+  ~
+  ~       http://www.apache.org/licenses/LICENSE-2.0
+  ~
+  ~  Unless required by applicable law or agreed to in writing, software
+  ~  distributed under the License is distributed on an "AS IS" BASIS,
+  ~  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  ~  See the License for the specific language governing permissions and
+  ~  limitations under the License.
+  -->
+<service name="SecureService7">
+
+	<module ref="addressing"/>
+	<module ref="rampart"/>
+
+	<parameter locked="false" name="ServiceClass">org.apache.rampart.Service</parameter>
+
+	<operation name="echo">
+		<messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
+		<actionMapping>urn:echo</actionMapping>
+	</operation>
+	
+	<wsp:Policy wsu:Id="SigEncrTripleDesRSA15DK" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
+	<wsp:ExactlyOne>
+		<wsp:All>
+			<sp:AsymmetricBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+				<wsp:Policy>
+					<sp:InitiatorToken>
+						<wsp:Policy>
+							<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
+								<wsp:Policy>
+									<sp:RequireDerivedKeys/>
+									<sp:WssX509V3Token10/>
+								</wsp:Policy>
+							</sp:X509Token>
+						</wsp:Policy>
+					</sp:InitiatorToken>
+					<sp:RecipientToken>
+						<wsp:Policy>
+							<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
+								<wsp:Policy>
+									<sp:RequireDerivedKeys/>
+									<sp:WssX509V3Token10/>
+								</wsp:Policy>
+							</sp:X509Token>
+						</wsp:Policy>
+					</sp:RecipientToken>
+					<sp:AlgorithmSuite>
+						<wsp:Policy>
+							<sp:TripleDesRsa15/>
+						</wsp:Policy>
+					</sp:AlgorithmSuite>
+					<sp:Layout>
+						<wsp:Policy>
+							<sp:Strict/>
+						</wsp:Policy>
+					</sp:Layout>
+					<sp:IncludeTimestamp/>
+					<sp:OnlySignEntireHeadersAndBody/>
+				</wsp:Policy>
+			</sp:AsymmetricBinding>
+			<sp:Wss10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+				<wsp:Policy>
+					<sp:MustSupportRefKeyIdentifier/>
+					<sp:MustSupportRefIssuerSerial/>
+				</wsp:Policy>
+			</sp:Wss10>
+			<sp:SignedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+				<sp:Body/>
+			</sp:SignedParts>
+			<sp:EncryptedParts xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
+				<sp:Body/>
+			</sp:EncryptedParts>
+
+			<ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy"> 
+				<ramp:user>alice</ramp:user>
+				<ramp:encryptionUser>bob</ramp:encryptionUser>
+				<ramp:passwordCallbackClass>org.apache.rampart.PWCallback</ramp:passwordCallbackClass>
+				
+				<ramp:signatureCrypto>
+					<ramp:crypto provider="org.apache.ws.security.components.crypto.Merlin">
+						<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property>
+						<ramp:property name="org.apache.ws.security.crypto.merlin.file">store.jks</ramp:property>
+						<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.password">password</ramp:property>
+					</ramp:crypto>
+				</ramp:signatureCrypto>
+				<ramp:encryptionCypto>
+					<ramp:crypto provider="org.apache.ws.security.components.crypto.Merlin">
+						<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property>
+						<ramp:property name="org.apache.ws.security.crypto.merlin.file">store.jks</ramp:property>
+						<ramp:property name="org.apache.ws.security.crypto.merlin.keystore.password">password</ramp:property>
+					</ramp:crypto>
+				</ramp:encryptionCypto>
+			</ramp:RampartConfig>
+
+		</wsp:All>
+	</wsp:ExactlyOne>
+	</wsp:Policy>
+</service>

Modified: webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/security-module.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/security-module.html Mon Jan 22 21:34:03 2007
@@ -1,249 +1,296 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type" content="">
-  <title>Rampart : WS-Security module for Axis2</title>
-  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
-</head>
-
-<body>
-<h1>Securing SOAP Messages with WSS4J</h1>
-
-<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security
-features, called "rampart". This document explains how to engage and
-configure rampart module.</p>
-
-<h2>Content</h2>
-<ul>
-  <li><a href="#intro">Introduction</a></li>
-  <li><a href="#outflowsecurity">OutflowSecurity Parameter</a></li>
-  <li><a href="#inflowsecurity">InflowSecurity Parameter</a></li>
-  <li><a href="#references">References</a></li>
-  <li><a href="#examples">Examples</a></li>
-</ul>
-<a name="intro"></a>
-
-<h2>Introduction</h2>
-
-<p>Since rampart module inserts handlers in the system specific pre-dispatch
-phase, it must be engaged globally. But it is possible to activate rampart
-module for the inflow or the outflow when required by the service or the
-clients.</p>
-
-<p>The rampart module (rampart.mar) is available with the Axis2 release.</p>
-
-<p>First it should be engaged by inserting the following in the axis2.xml
-file.</p>
-<source><pre>    &lt;module ref="rampart"/&gt;</pre>
-</source>
-<p>The web admin interface can be used when Axis2 is deployed in a servlet
-container such as Apache Tomcat.</p>
-
-<p>At the server it is possible to provide security on a per service basis.
-The configuration parameters should be set in the service.xml file of the
-service. The client side config parameters should be set in the axis2.xml of
-the client's Axis2 repository.</p>
-
-<p>Aegis module uses two parameters:</p>
-<ul>
-  <li>OutflowSecurity</li>
-  <li>InflowSecurity</li>
-</ul>
-The configuration that can go in each of these parameters are described
-below: <a name="outflowsecurity"></a>
-
-<h2>OutflowSecurity Parameter</h2>
-This parameter is used to configure the outflow security handler. The outflow
-handler can be invoked more than once in the outflow one can provide
-configuration for each of these invocations. The 'action' element describes
-one of these configurations. Therefore the 'OutflowSecurity' parameter can
-contain more than one 'action' elements. The schema of this 'action' element
-is available <a href="sec-conf/out-action.xsd">here</a>.
-
-<p>An outflow configuration to add a timestamp, sign and encrypt the message
-once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1"> Example
-2</a> shows how to sign the message twice by chaining the outflow handler
-(using two 'action' elements)</p>
-
-<p>Following is a description of the elements that can go in an 'action'
-element of the OutflowSecurity parameter</p>
-<br>
-
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td><b>Parameter</b></td>
-      <td><b>Description</b></td>
-      <td><b>Example</b></td>
-    </tr>
-    <tr>
-      <td>items</td>
-      <td>Security actions for the inflow</td>
-      <td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br>
-        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
-    </tr>
-    <tr>
-      <td>user</td>
-      <td>The user's name</td>
-      <td>Set alias of the key to be used to sign<br>
-        &lt;user&gt; bob&lt;/user&gt;</td>
-    </tr>
-    <tr>
-      <td>passwordCallbackClass</td>
-      <td>Callback class used to provide the password required to create the
-        UsernameToken or to sign the message</td>
-      <td>&lt;passwordCallbackClass&gt;
-        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
-    </tr>
-    <tr>
-      <td>signaturePropFile</td>
-      <td>property file used to get the signature parameters such as crypto
-        provider, keystore and its password</td>
-      <td>Set example.properties file as the signature property file<br>
-        &lt;signaturePropFile&gt;
-      example.properties&lt;/signaturePropFile&gt;</td>
-    </tr>
-    <tr>
-      <td>signatureKeyIdentifier</td>
-      <td>Key identifier to be used in referring the key in the signature</td>
-      <td>Use the serial number of the certificate<br>
-        &lt;signatureKeyIdentifier&gt;
-        IssuerSerial&lt;/signatureKeyIdentifier&gt;</td>
-    </tr>
-    <tr>
-      <td>encryptionKeyIdentifier</td>
-      <td>Key identifier to be used in referring the key in encryption</td>
-      <td>Use the serial number of the certificate <br>
-        &lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;</td>
-    </tr>
-    <tr>
-      <td>encryptionUser</td>
-      <td>The user's name for encryption.</td>
-      <td><br>
-        &lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
-    </tr>
-    <tr>
-      <td>encryptionSymAlgorithm</td>
-      <td>Symmetric algorithm to be used for encryption</td>
-      <td>Use AES-128<br>
-        &lt;encryptionSymAlgorithm&gt;
-        http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
-    </tr>
-    <tr>
-      <td>encryptionKeyTransportAlgorithm</td>
-      <td>Key encryption algorithm</td>
-      <td>Use RSA-OAEP<br>
-        &lt;parameter name="encryptionSymAlgorithm"&gt;
-        http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</td>
-    </tr>
-    <tr>
-      <td>signatureParts</td>
-      <td>Sign multiple parts in the SOAP message</td>
-      <td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br>
-        &lt;signatureParts&gt;
-        {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar
-        &lt;/signatureParts&gt;</td>
-    </tr>
-    <tr>
-      <td>optimizeParts</td>
-      <td>MTOM Optimize the elements specified by the XPath query</td>
-      <td>Optimize the CipherValue<br>
-        &lt;optimizeParts&gt;
-        //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue
-        &lt;/optimizeParts&gt;</td>
-    </tr>
-  </tbody>
-</table>
-<a name="inflowsecurity"></a>
-
-<h2>InflowSecurity Parameter</h2>
-
-<p>This parameter is used to configure the inflow security handler. The
-'action' element is used to encapsulate the configuration elements here as
-well. The schema of the 'action' element is available here. <a
-href="#ex3">Example 3</a> shows the configuration to decrypt, verify
-signature and validate timestamp.</p>
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td><b>Parameter</b></td>
-      <td><b>Description</b></td>
-      <td><b>Example</b></td>
-    </tr>
-    <tr>
-      <td>items</td>
-      <td>Security actions for the inflow</td>
-      <td>first the incoming message should be decrypted and then the
-        signatures should be verified and should be checked for the
-        availability of the Timestamp <br>
-        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
-    </tr>
-    <tr>
-      <td>passwordCallbackClass</td>
-      <td>Callback class used to obtain password for decryption and
-        UsernameToken verification</td>
-      <td><br>
-        &lt;passwordCallbackClass&gt;
-        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
-    </tr>
-    <tr>
-      <td>signaturePropFile</td>
-      <td>Property file used for signature verification</td>
-      <td><br>
-        &lt;signaturePropFile&gt;
-      sig.properties&lt;/signaturePropFile&gt;</td>
-    </tr>
-    <tr>
-      <td>decryptionPropFile</td>
-      <td>Property file used for decryption</td>
-      <td><br>
-        &lt;decryptionPropFile&gt;
-      dec.properties&lt;/decryptionPropFile&gt;</td>
-    </tr>
-  </tbody>
-</table>
-<br>
-
-
-<p>Please note that the '.properties' files used in properties such as
-OutSignaturePropFile are the same property files that are using in the WSS4J
-project. Following shows the properties defined in a sample property file</p>
-<source><pre>        org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
-        org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
-        org.apache.ws.security.crypto.merlin.keystore.password=security
-        org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
-        org.apache.ws.security.crypto.merlin.alias.password=security
-        org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
-    </pre>
-</source>org.apache.ws.security.crypto.provider defines the implementation of
-the org.apache.ws.security.components.crypto.Crypto interface to provide the
-crypto information required by WSS4J. The other properties defined are the
-configuration properties used by the implementation class
-(org.apache.ws.security.components.crypto.Merlin). <a name="ref"></a> <a
-name="references"></a>
-
-<h2>References</h2>
-
-<p>1. <a href="http://ws.apache.org/wss4j">Apache WSS4J -Home</a></p>
-<a name="examples"></a>
-
-<h2>Examples</h2>
-
-<p id="ex1">Example 1: An outflow configuration to add a timestamp, sign and
-encrypt the message once</p>
-
-<p><img alt="" src="sec-conf/out-sample.png"></p>
-
-<p id="ex2">Example 2: An outflow configuration to sign the message twice and
-add a timestamp</p>
-
-<p><img alt="" src="sec-conf/out-sample2.png"></p>
-
-<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature
-and validate timestamp</p>
-
-<p><img alt="" src="sec-conf/in-sample.png"></p>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <link href="../../../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
+  <title>Rampart : WS-Security module for Axis2</title>
+</head>
+
+<body>
+<h1>Securing SOAP Messages with Rampart</h1>
+
+<p>Axis2 comes with a module based on Apache WSS4J [1] to provide WS-Security
+features, called "Rampart". This document explains how to engage and
+configure Rampart module.</p>
+
+<h2>Content</h2>
+<ul>
+  <li><a href="#intro">Introduction</a></li>
+    <li><a href="#1_1_config">Rampart-1.1 Configuration</a>
+	<ul>
+	<li><a href="#1_1_assetions">Rampart Specific Assertions</a></li>
+	<li><a href="#1_1_service_config">Service Configration</a></li>
+	<li><a href="#1_1_client_config">Client Confiuration</a></li>
+	</ul></li>
+  <li><a href="#1_0_config">Rampart-1.0 Configuration</a>
+  <ul>
+  <li><a href="#outflowsecurity">OutflowSecurity Parameter</a></li>
+  <li><a href="#inflowsecurity">InflowSecurity Parameter</a></li>
+  </ul></li>
+  <li><a href="#references">References</a></li>
+  <li><a href="#examples">Examples</a></li>
+</ul>
+<a name="intro"></a>
+
+<h2>Introduction</h2>
+
+<p>Since rampart module inserts handlers in the system specific security
+phase, it must be engaged globally. These handlers can be configured 
+using WS-SecurityPolicy[2] and Rampart specific policy assertions. 
+Rampart-1.0 used two axis2 parameters for configuration and these are
+still supported in the 1.1 release as well.</p>
+
+<p>The rampart-1.1 release is available 
+<a href="http://www.apache.org/dyn/closer.cgi/ws/rampart/1_1">here</a>.</p>
+
+<p>First it should be engaged by inserting the following in the axis2.xml
+file.</p>
+<source><pre>    &lt;module ref="rampart"/&gt;</pre>
+</source>
+<p>The web admin interface can be used when Axis2 is deployed in a servlet
+container such as Apache Tomcat.</p>
+
+<p>At the server it is possible to provide security on a per service basis.
+The configuration parameters should be set in the service.xml file of the
+service. The client side config parameters should be set in the axis2.xml of
+the client's Axis2 repository.</p>
+<a id="1_1_config"></a>
+<h2>Rampart-1.1 Configuration</h2>
+<a id="1_1_assetions"></a>
+<h3>Rampart Specific Assertions</h3>
+
+<p>Rampart uses the standard WS-SecurityPolicy[2] assertions and also defines its own 
+assertions to be able capture the configuration information that is not provided 
+in WS-SecurityPolicy.</p>
+<p>The Rampart specific assertion's xsd can be found <a href="sec-conf/rampart-config.xsd">here
+</a>.</p>
+
+<p>The <strong>ramp:RampartConfig</strong> assertion must be available as a one of the top 
+level assertions of the policy as shown <a href="sec-conf/sample-policy.xml">here</a>.</p>
+<a id="1_1_service_config"></a>
+<h3>Service Configration</h3>
+
+To configure the service one will simply have to add the policy element into the 
+sevices.xml file. A sample service.xml file is available 
+<a href="sec-conf/sample-services.xml">here</a>.
+<a id="1_1_client_config"></a>
+<h3>Client Confiuration</h3>
+<p>On the client side, a policy object should be created and loaded into options. Creating the policy object can be done using a "policy.xml" file as follows.</p>
+	
+<pre>
+	//Creating the object
+  	StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile);
+        Policy clientPolicy = PolicyEngine.getPolicy(builder.getDocumentElement());
+	//setting the object
+	Options options = new Options();
+        options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, clientPolicy);
+</pre>
+<a id="1_0_config"></a>
+<h2>Rampart-1.0 Configuration</h2>
+
+<p>Rampart module uses two parameters:</p>
+<ul>
+  <li><a href="outflowsecurity">OutflowSecurity</a></li>
+  <li><a href="inflowsecurity">InflowSecurity</a></li>
+</ul>
+The configuration that can go in each of these parameters are described
+below: <a name="outflowsecurity"></a>
+
+<h3>OutflowSecurity Parameter</h3>
+This parameter is used to configure the outflow security handler. The outflow
+handler can be invoked more than once in the outflow one can provide
+configuration for each of these invocations. The 'action' element describes
+one of these configurations. Therefore the 'OutflowSecurity' parameter can
+contain more than one 'action' elements. The schema of this 'action' element
+is available <a href="sec-conf/out-action.xsd">here</a>.
+
+<p>An outflow configuration to add a timestamp, sign and encrypt the message
+once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1"> Example
+2</a> shows how to sign the message twice by chaining the outflow handler
+(using two 'action' elements)</p>
+
+<p>Following is a description of the elements that can go in an 'action'
+element of the OutflowSecurity parameter</p>
+<br>
+
+
+<table border="1">
+  <tbody>
+    <tr>
+      <td><b>Parameter</b></td>
+      <td><b>Description</b></td>
+      <td><b>Example</b></td>
+    </tr>
+    <tr>
+      <td>items</td>
+      <td>Security actions for the inflow</td>
+      <td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br>
+        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
+    </tr>
+    <tr>
+      <td>user</td>
+      <td>The user's name</td>
+      <td>Set alias of the key to be used to sign<br>
+        &lt;user&gt; bob&lt;/user&gt;</td>
+    </tr>
+    <tr>
+      <td>passwordCallbackClass</td>
+      <td>Callback class used to provide the password required to create the
+        UsernameToken or to sign the message</td>
+      <td>&lt;passwordCallbackClass&gt;
+        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
+    </tr>
+    <tr>
+      <td>signaturePropFile</td>
+      <td>property file used to get the signature parameters such as crypto
+        provider, keystore and its password</td>
+      <td>Set example.properties file as the signature property file<br>
+        &lt;signaturePropFile&gt;
+      example.properties&lt;/signaturePropFile&gt;</td>
+    </tr>
+    <tr>
+      <td>signatureKeyIdentifier</td>
+      <td>Key identifier to be used in referring the key in the signature</td>
+      <td>Use the serial number of the certificate<br>
+        &lt;signatureKeyIdentifier&gt;
+        IssuerSerial&lt;/signatureKeyIdentifier&gt;</td>
+    </tr>
+    <tr>
+      <td>encryptionKeyIdentifier</td>
+      <td>Key identifier to be used in referring the key in encryption</td>
+      <td>Use the serial number of the certificate <br>
+        &lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;</td>
+    </tr>
+    <tr>
+      <td>encryptionUser</td>
+      <td>The user's name for encryption.</td>
+      <td><br>
+        &lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
+    </tr>
+    <tr>
+      <td>encryptionSymAlgorithm</td>
+      <td>Symmetric algorithm to be used for encryption</td>
+      <td>Use AES-128<br>
+        &lt;encryptionSymAlgorithm&gt;
+        http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
+    </tr>
+    <tr>
+      <td>encryptionKeyTransportAlgorithm</td>
+      <td>Key encryption algorithm</td>
+      <td>Use RSA-OAEP<br>
+        &lt;parameter name="encryptionSymAlgorithm"&gt;
+        http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</td>
+    </tr>
+    <tr>
+      <td>signatureParts</td>
+      <td>Sign multiple parts in the SOAP message</td>
+      <td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br>
+        &lt;signatureParts&gt;
+        {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar
+        &lt;/signatureParts&gt;</td>
+    </tr>
+    <tr>
+      <td>optimizeParts</td>
+      <td>MTOM Optimize the elements specified by the XPath query</td>
+      <td>Optimize the CipherValue<br>
+        &lt;optimizeParts&gt;
+        //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue
+        &lt;/optimizeParts&gt;</td>
+    </tr>
+  </tbody>
+</table>
+<a name="inflowsecurity"></a>
+
+<h3>InflowSecurity Parameter</h3>
+
+<p>This parameter is used to configure the inflow security handler. The
+'action' element is used to encapsulate the configuration elements here as
+well. The schema of the 'action' element is available here. <a
+href="#ex3">Example 3</a> shows the configuration to decrypt, verify
+signature and validate timestamp.</p>
+
+<table border="1">
+  <tbody>
+    <tr>
+      <td><b>Parameter</b></td>
+      <td><b>Description</b></td>
+      <td><b>Example</b></td>
+    </tr>
+    <tr>
+      <td>items</td>
+      <td>Security actions for the inflow</td>
+      <td>first the incoming message should be decrypted and then the
+        signatures should be verified and should be checked for the
+        availability of the Timestamp <br>
+        &lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
+    </tr>
+    <tr>
+      <td>passwordCallbackClass</td>
+      <td>Callback class used to obtain password for decryption and
+        UsernameToken verification</td>
+      <td><br>
+        &lt;passwordCallbackClass&gt;
+        org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
+    </tr>
+    <tr>
+      <td>signaturePropFile</td>
+      <td>Property file used for signature verification</td>
+      <td><br>
+        &lt;signaturePropFile&gt;
+      sig.properties&lt;/signaturePropFile&gt;</td>
+    </tr>
+    <tr>
+      <td>decryptionPropFile</td>
+      <td>Property file used for decryption</td>
+      <td><br>
+        &lt;decryptionPropFile&gt;
+      dec.properties&lt;/decryptionPropFile&gt;</td>
+    </tr>
+  </tbody>
+</table>
+<br>
+
+
+<p>Please note that the '.properties' files used in properties such as
+OutSignaturePropFile are the same property files that are using in the WSS4J
+project. Following shows the properties defined in a sample property file</p>
+<source><pre>        org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
+        org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
+        org.apache.ws.security.crypto.merlin.keystore.password=security
+        org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
+        org.apache.ws.security.crypto.merlin.alias.password=security
+        org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
+    </pre>
+</source>org.apache.ws.security.crypto.provider defines the implementation of
+the org.apache.ws.security.components.crypto.Crypto interface to provide the
+crypto information required by WSS4J. The other properties defined are the
+configuration properties used by the implementation class
+(org.apache.ws.security.components.crypto.Merlin). <a name="ref"></a> <a
+name="references"></a>
+
+<h2>References</h2>
+
+<p>1. <a href="http://ws.apache.org/wss4j">Apache WSS4J -Home</a></p>
+<a name="examples"></a>
+<p>2. <a href="http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf">ws-securitypolicy.pdf</a></p>
+<a name="examples"></a>
+
+
+<h2>Examples</h2>
+
+<p id="ex1">Example 1: An outflow configuration to add a timestamp, sign and
+encrypt the message once</p>
+
+<p><img alt="" src="sec-conf/out-sample.png"></p>
+
+<p id="ex2">Example 2: An outflow configuration to sign the message twice and
+add a timestamp</p>
+
+<p><img alt="" src="sec-conf/out-sample2.png"></p>
+
+<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature
+and validate timestamp</p>
+
+<p><img alt="" src="sec-conf/in-sample.png"></p>
+</body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/modules/wss4j/0_94/0.94/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/wss4j/0_94/0.94/security-module.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/wss4j/0_94/0.94/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/wss4j/0_94/0.94/security-module.html Mon Jan 22 21:34:03 2007
@@ -2,6 +2,7 @@
 <html>
 <head>
   <meta http-equiv="content-type" content="">
+<link href="../../../../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
   <title>The Security Module</title>
 </head>
 

Modified: webservices/axis2/trunk/java/xdocs/modules/wss4j/0_95/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/wss4j/0_95/security-module.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/wss4j/0_95/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/wss4j/0_95/security-module.html Mon Jan 22 21:34:03 2007
@@ -2,6 +2,7 @@
 <html>
 <head>
   <meta http-equiv="content-type" content="">
+<link href="../../../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
   <title>The Security Module</title>
 </head>
 

Modified: webservices/axis2/trunk/java/xdocs/modules/wss4j/1_0/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/modules/wss4j/1_0/security-module.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/modules/wss4j/1_0/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/modules/wss4j/1_0/security-module.html Mon Jan 22 21:34:03 2007
@@ -2,6 +2,7 @@
 <html>
 <head>
   <meta http-equiv="content-type" content="">
+  <link href="../../../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
   <title>Rampart : WS-Security module for Axis2</title>
 </head>
 

Modified: webservices/axis2/trunk/java/xdocs/navigation.xml
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/navigation.xml?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/navigation.xml (original)
+++ webservices/axis2/trunk/java/xdocs/navigation.xml Mon Jan 22 21:34:03 2007
@@ -18,7 +18,7 @@
 			<item name="Tools" href="tools/index.html" />
 		</menu>
 		<menu name="Documentation">
-			<item name="Version 1.1" href="/1_1/contents.html" >
+			<item name="Version 1.1.1" href="/1_1/contents.html" >
 			   <item name="Table of Contents" href="1_1/toc.html" />
 			   <item name="Installation Guide" href="1_1/installationguide.html" />
 			   <item name="QuickStart Guide" href="1_1/quickstartguide.html" />

Modified: webservices/axis2/trunk/java/xdocs/tools/1_1/CodegenToolReference.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/tools/1_1/CodegenToolReference.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/tools/1_1/CodegenToolReference.html (original)
+++ webservices/axis2/trunk/java/xdocs/tools/1_1/CodegenToolReference.html Mon Jan 22 21:34:03 2007
@@ -395,20 +395,20 @@
 <p>For this Ant task to work the following jars need to be in the class
     path.</p>
 <ul>
-    <li>axis-*.jar (from the Axis2 distribution)</li>
-    <li>wsdl4j-1.5.1.jar or higher (The WSDL4J implementation jar. Bundled with
+    <li>axis2-*.jar (from the Axis2 distribution)</li>
+    <li>wsdl4j-1.6.2.jar or higher (The WSDL4J implementation jar. Bundled with
         the Axis2 distribution)</li>
     <li>stax-api-1.0.1.jar (The StAX API's that contain the
         javax.xml.namespace.QName class. This jar may be replaced by any other
         jar that contains the javax.xml.namespace.QName implementation. However
         Axis2 uses this class from the stax-api-1.0.1.jar which comes bundled
         with the Axis2 distribution)</li>
-    <li>commons-logging-1.1.jar, neethi-1.1.jar and XmlSchema-1.1.jar (from the
+    <li>commons-logging-1.1.jar, neethi-2.0.jar and XmlSchema-1.2.jar (from the
         Axis2 distribution)</li>
-    <li>axiom-api-1.1.1.jar and axiom-impl-1.1.1.jar (from the Axis2
+    <li>axiom-api-1.2.1.jar and axiom-impl-1.2.1.jar (from the Axis2
         distribution)</li>
     <li>activation-1.1.jar (from the Axis2 distribution)</li>
-    <li>astx-asl0-3.0.1.jar (from the Axis2 distribution)</li>
+    <li>wstx-asl-3.1.0.jar (from the Axis2 distribution)</li>
 </ul>
 <a name="invoking"></a>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org