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 ch...@apache.org on 2006/03/10 10:09:36 UTC
svn commit: r384737 - in /webservices/axis2/trunk/java/xdocs:
archived_news.html index.html latest/WS_policy.html latest/userguide1.html
Author: chatra
Date: Fri Mar 10 01:09:36 2006
New Revision: 384737
URL: http://svn.apache.org/viewcvs?rev=384737&view=rev
Log:
updating docs for 0.95
Modified:
webservices/axis2/trunk/java/xdocs/archived_news.html
webservices/axis2/trunk/java/xdocs/index.html
webservices/axis2/trunk/java/xdocs/latest/WS_policy.html
webservices/axis2/trunk/java/xdocs/latest/userguide1.html
Modified: webservices/axis2/trunk/java/xdocs/archived_news.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/archived_news.html?rev=384737&r1=384736&r2=384737&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/archived_news.html (original)
+++ webservices/axis2/trunk/java/xdocs/archived_news.html Fri Mar 10 01:09:36 2006
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
@@ -11,13 +11,29 @@
<body>
<h1>Apache Axis2 Archived News</h1>
+
+<p>This document will contain details on each of the Axis2 versions that were
+released up to the currect version.</p>
+
+<h2>Content</h2>
+<h3>Apache Axis2 Releases:</h3>
+<ul>
+ <li><a href="#0_94">11 January 2006- Version0.94</a></li>
+ <li><a href="#0_93">02 December 2005 - Version 0.93</a></li>
+ <li><a href="#0_92">26 September 2005 - Version 0.92</a></li>
+ <li><a href="#0_91">12 August 2005 - Version 0.91</a></li>
+ <li><a href="#0_90">02 July 2005 - Version 0.9</a></li>
+ <li><a href="#M2">07 June 2005 - Milestone 2</a></li>
+ <li><a href="#M1">24 February 2005 - Milestone 1</a></li>
+</ul>
+<a name="0_94"></a>
<h2>11 January 2006 - Apache Axis2 Version 0.94 Released! (<a
href="http://ws.apache.org/axis2/download.cgi">Download 0.94</a>)</h2>
<p>This release includes the following features:</p>
-<h3 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Complete
-Features List</h3>
+<h3 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Complete Features
+List</h3>
<ol type="1">
<li>AXIOM, an XML object model working on StAX (Streaming API for XML)
parsing optimized for SOAP 1.1/1.2 Messages. This has complete XML
@@ -42,13 +58,14 @@
<li>Support for MTOM/ MIME/ SwA</li>
<li>SAAJ implementation</li>
<li>DOOM - <span style="color: #FF0000">New</span></li>
- <li>Pack/Unpack capability for the generated code- <span style="color: #FF0000">New</span></li>
+ <li>Pack/Unpack capability for the generated code- <span
+ style="color: #FF0000">New</span></li>
<li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
<li>Numerous bug fixes since last release</li>
</ol>
-<h3 id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad">Axis2 Experimental
-Features List</h3>
+<h4 id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad">Axis2 Experimental
+Features List</h4>
<ol type="1">
<li>Sessions scoping for Application, SOAP, Transport and Request
levels</li>
@@ -92,13 +109,12 @@
such as JSR 109 support</li>
<li>Completion of interop tests</li>
</ol>
-
-
+<a name="0_93"></a>
<h2>02 December 2005 - Apache Axis2 Version 0.93 Released! ( <a
href="http://ws.apache.org/axis2/download.cgi">Download 0.93</a>)</h2>
<p>Axis2 is becoming more and more stable. <a
-href="http://ws.apache.org/axis2/download.cgi">Download it!. </a>This 0.93
+href="http://ws.apache.org/axis2/download.cgi">Download it!.</a>This 0.93
release contains the following additional features:</p>
<ul>
<li>JDK 1.5 compatibility</li>
@@ -112,12 +128,14 @@
<li>support for rpc/literal</li>
<li>And numerous bug fixes after 0.92 release</li>
</ul>
+
<h3>Experimental features list</h3>
<ol type="1">
<li>DOOM - DOM implementation over OM</li>
<li>Java2WSDL</li>
<li>RPC Support</li>
</ol>
+
<h3>Major changes since last release</h3>
<ol>
<li>Refactored org.apache.axis2.clientapi to org.apache.axis2.client</li>
@@ -129,7 +147,7 @@
We are getting closer to a 1.0 release, the remaining tasks to be completed
before a 1.0 release include: SOAP 1.1 and 1.2 validation, Our own data
binding implementation, WSDL Generation.
-
+<a name="0_92"></a>
<h2>26 September 2005 - Apache Axis2 Version 0.92 Released! <a
href="http://ws.apache.org/axis2/download.cgi">(Download 0.92)</a></h2>
@@ -156,7 +174,7 @@
<p><em>We are getting closer to a 1.0 release, the remaining tasks to be
completed before a 1.0 release include: SOAP 1.1 and 1.2 validation, Our own
data binding implementation, WSDL Generation.</em></p>
-
+<a name="0_91"></a>
<h2>12 August 2005 - Apache Axis2 Version 0.91 Released! <a
href="http://ws.apache.org/axis2/download.cgi">(Download 0.91)</a></h2>
@@ -172,7 +190,7 @@
<li>Improved code generation templates</li>
<li>Numerous bug fixes</li>
</ul>
-
+<a name="0_90"></a>
<h2>02 July 2005 - Apache Axis2 Version 0.9 Released! <a
href="releases.html#0.9">(Download 0.9)</a></h2>
@@ -186,7 +204,7 @@
<li>MTOM/SWA attachments support</li>
<li>SAAJ implementation</li>
</ul>
-
+<a name="M2"></a>
<h2>07 June 2005 - Apache Axis2 Milestone 2 (M2) Released</h2>
<p>Apache Axis2 is starting to take shape, features implemented in this
@@ -206,7 +224,7 @@
<li>Service Archive Wizard- Eclipse plug-in</li>
<li>Module Archive Wizard-Eclipse plug-in</li>
</ul>
-
+<a name="M1"></a>
<h2>24 February 2005 - Apache Axis2 Milestone 1 (M1) Released</h2>
<p>This first milestone release of Axis2 includes the following features:</p>
@@ -222,6 +240,5 @@
transport</li>
<li>Hot deployment of Web Services</li>
</ul>
-
</body>
</html>
Modified: webservices/axis2/trunk/java/xdocs/index.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/index.html?rev=384737&r1=384736&r2=384737&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/index.html Fri Mar 10 01:09:36 2006
@@ -40,11 +40,11 @@
protocols including:</p>
<ul>
<li><a
- href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrm">WS-ReliableMessaging</a></li>
+ href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrm" target="_blank">WS-ReliableMessaging</a></li>
<li><a
- href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss">WS-Security</a></li>
+ href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss" target="_blank">WS-Security</a></li>
<li><a
- href="http://www.w3.org/Submission/ws-addressing/">WS-Addressing</a></li>
+ href="http://www.w3.org/Submission/ws-addressing/" target="_blank">WS-Addressing</a></li>
</ul>
<h2>Latest Release</h2>
@@ -56,6 +56,7 @@
<h3 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Axis2 Complete
Features List</h3>
+
<ol type="1">
<li>AXIOM, an XML object model working on StAX (Streaming API for XML) parsing optimized for SOAP 1.1/1.2 Messages. This has complete XML infoset support.</li>
<li>Support for One-Way Messaging (In-Only) and Request Response Messaging (In-Out)</li>
@@ -84,17 +85,19 @@
<li>Loading module (.mar) from classpath-<span style="color: #FF0000">New</span></li>
</ol>
-<h3 id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad">Axis2 Experimental
-Features List</h3>
+<h4 id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad">Axis2 Experimental
+Features List</h4>
+
<ol type="1">
<li>Sessions scoping for Application, SOAP, Transport and Request levels</li>
- <li>Server side Web Service Policy support</li>
+ <li>Server side & client side Web Service Policy support</li>
<li>?wsdl and ?xsd support</li>
<li>Generating ServiceClient for a given WSDL and invoke the corresponding service using generated client.</li>
</ol>
<h3 id="head-7dd8e783bb9e22fb00f88748855bb6e500111e12">Major Changes Since
Last Release</h3>
+
<ol type="1">
<li>Transport framework improvements (ListenerManager)</li>
<li>Changed the way of adding action to mapping (wsamapping) from parameter to child element so with this version onward the way of adding mapping is as follows:</li>
@@ -172,13 +175,13 @@
set of options for client-server interaction.</p>
<h2>Archived News</h2>
-<p><b>11 January 2006 - Apache Axis2 Version 0.94 Released! (<a
-href="http://ws.apache.org/axis2/download.cgi">Download 0.94</a>)</b></p>
+<h3>11 January 2006 - Apache Axis2 Version 0.94 Released! (<a
+href="http://ws.apache.org/axis2/download.cgi">Download 0.94</a>)</h3>
<p>This release includes the following features:</p>
-<p id="head-215f3945a40558f9ad055ed5b6601e8f93706558"><b>Complete
-Features List</b></p>
+<h4 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Complete
+Features List</h4>
<ol type="1">
<li>AXIOM, an XML object model working on StAX (Streaming API for XML)
parsing optimized for SOAP 1.1/1.2 Messages. This has complete XML
@@ -220,8 +223,8 @@
service using generated client.</li>
</ol>
-<p id="head-7dd8e783bb9e22fb00f88748855bb6e500111e12"><b>Major Changes Since
-Last Release</b></p>
+<h4 id="head-7dd8e783bb9e22fb00f88748855bb6e500111e12">Major Changes Since
+Last Release</h4>
<ol type="1">
<li>Fixing of memory leaks</li>
<li>Client API changes , Introducing ServiceClient instead of MEPClient,
@@ -233,16 +236,16 @@
<li>Packing and unpacking options for the code generated classes</li>
</ol>
-<p id="head-83371cc3d6961295be042f584c7b74d81cca23c4"><b>Tools Included In This
-Release</b></p>
+<h4 id="head-83371cc3d6961295be042f584c7b74d81cca23c4">Tools Included In This
+Release</h4>
<ol type="1">
<li>Axis2 Web Application (Web App)</li>
<li>WSDL2WS- Eclipse plugin/ Command line version/ IntelliJ IDEA plugin</li>
<li>Service Archive Wizard- Eclipse plugin/ IntelliJ IDEA plugin</li>
</ol>
-<p id="head-599c5a50552f02ebdeb5f58ef8da289234812ca4"><b>What's Still To
-Do?</b></p>
+<h4 id="head-599c5a50552f02ebdeb5f58ef8da289234812ca4">What's Still To
+Do?</h4>
<ol type="1">
<li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
<li>SOAP Encoding</li>
@@ -255,8 +258,8 @@
</ol>
-<p><b>02 December 2005 - Apache Axis2 Version 0.93 Released! (</b> <a
-href="http://ws.apache.org/axis2/download.cgi">Download 0.93</a>)</p>
+<h3>02 December 2005 - Apache Axis2 Version 0.93 Released! ( <a
+href="http://ws.apache.org/axis2/download.cgi">Download 0.93</a>)</h3>
<p>Axis2 is becoming more and more stable. <a
href="http://ws.apache.org/axis2/download.cgi">Download it!. </a>This 0.93
@@ -273,13 +276,13 @@
<li>support for rpc/literal</li>
<li>And numerous bug fixes after 0.92 release</li>
</ul>
-<b>Experimental features list</b>
+<p><b>Experimental features list</b></p>
<ol type="1">
<li>DOOM - DOM implementation over OM</li>
<li>Java2WSDL</li>
<li>RPC Support</li>
</ol>
-<b>Major changes since last release</b>
+<h4>Major changes since last release</h4>
<ol>
<li>Refactored org.apache.axis2.clientapi to org.apache.axis2.client</li>
<li>Introduction of Options to configure clients</li>
Modified: webservices/axis2/trunk/java/xdocs/latest/WS_policy.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/WS_policy.html?rev=384737&r1=384736&r2=384737&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/WS_policy.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/WS_policy.html Fri Mar 10 01:09:36 2006
@@ -1,61 +1,168 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
- <title>WS Policy Support in Axis2</title>
- <meta name="generator" content="amaya 9.2.1, see http://www.w3.org/Amaya/">
-</head>
-
-<body lang="en">
-<h1 align="center">Web Services Policy Support In Axis2</h1>
-
-<h2 align="center"><em>-Experimental Feature</em></h2>
-
-<p><em>Axis2 version 0.95</em></p>
-<i>E-mail comments/ suggestions to: <a
-href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
-
-<h2>What is Web Services (WS) Policy?</h2>
-
-<p>To consume non trivial web services one must fully understand its xml
-contract (WSDL) along with any other additional requirements, capabilities or
-preferences which translates to the configuration of the service, and
-essentially becomes the policies of the service.</p>
-
-<p>WS Policy framework provides a way to express the policies of a service in
-a machine-readable way. Web services infrastructure can be enhanced to
-understand and enforce policies at runtime. For instance, a service author
-might write a policy requiring digital signature and encryption, while
-service consumers could use the policy information to reason out whether they
-can adhere to this policy information to use the service or not.</p>
-
-<p>Further more, web service infrastructure could be enhanced to enforce
-those requirements without requiring the service author to write even single
-line of code.</p>
-
-<h2>What's in this release?</h2>
-
-<p>In this current release Axis2 framework uses ws-commons/policy as an
-object model to manipulate policy documents. All its description builders
-store any policy information included in description documents (services.xml,
-axis2.xml, .. etc) in the appropriate description classes. This information
-is available at both deployment and run time via these description
-classes.</p>
-
-<p>When generating WSDL dynamically for each service, policy information in
-the description classes is included. For instance, if you declare a policy in
-axis2.xml then that policy is reflected in service elements of WSDL of every
-service. If a policy is declared in a services.xml, it is shown in the
-service element of WSDL for that particular service.</p>
-
-<p>Next step is to use that information to engage and configure required
-modules and allow the module to make use of this policy information.</p>
-
-<p>It is evident that a great deal of work is required to make axis2 a fully
-fledged ws-policy supported web service infrastructure. But it is encouraging
-to note that we've taken the first steps towards this goal. We appreciate any
-suggestions, patches etc you send us in this regard. Keep on
-contributing...!</p>
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+ <title>WS Policy Support in Axis2</title>
+ <meta name="generator" content="amaya 9.2.1, see http://www.w3.org/Amaya/">
+</head>
+
+<body lang="en">
+<h1 align="center">Web Services Policy Support In Axis2</h1>
+
+<h2 align="center"><em>-Experimental Feature</em></h2>
+
+<p><em>Axis2 version 0.95</em></p>
+<i>E-mail comments/ suggestions to: <a
+href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
+
+<h2>What is Web Services (WS) Policy?</h2>
+
+<p>To consume non trivial web services one must fully understand its xml
+contract (WSDL) along with any other additional requirements, capabilities or
+preferences which translates to the configuration of the service, and
+essentially becomes the policies of the service.</p>
+
+<p>WS Policy framework provides a way to express the policies of a service in
+a machine-readable way. Web services infrastructure can be enhanced to
+understand and enforce policies at runtime. For instance, a service author
+might write a policy requiring digital signature and encryption, while
+service consumers could use the policy information to reason out whether they
+can adhere to this policy information to use the service or not.</p>
+
+<p>Further more, web service infrastructure could be enhanced to enforce
+those requirements without requiring the service author to write even single
+line of code.</p>
+
+<h2>Client Side WS-Policy Supprt</h2>
+
+<p>This release <strong>fully supports WS Policy at client-side</strong>. It
+means that when you codegen a stub against a WSLD which contains policies,
+the stub will contain the capability to engage the required modules with the
+appropriate configurations. For instance, if there is a security policy
+attached to an operation in the WSDL, the generated stub will engage the
+security module for that operation with the appropriate security
+configurations.</p>
+
+<h3>How it works:</h3>
+
+<h4>Phase1: At PolicyEvaluator</h4>
+
+<p>Codegen engine runs few of its registered extensions before it generates
+the stub. When PolicyEvalutor (which is a registered Codegen extension) is
+initialized, it populates a registry of namespaces of supported policies to
+PolicyExtensions.</p>
+
+<p>For instance module foo might have a mapping of namespace
+http://test.com/foo which means any primitive assertion which has this
+namespace will be processed by this module. That module might implements the
+ModulePolicyExtension interface via PolicyExtension object can be
+obtained.</p>
+
+<p>A PolicyExtension is the access point for a module to add any other
+methods to the stub. For instance Reliable Messaging module can add
+createSequence() and endSequence() methods to the stub, that the user must
+call to start a RM sequence and ends a sequence.</p>
+
+<p>Then at the engagement of PolicyEvaluator, effective policy of each
+operation is calculated based on policy information declared in the WSDL
+document. Here we assumes that effective policy of an operation contains a
+single alternative (Multiple policy alternatives are not supported). Then we
+split that policy into few other policies such that each policy will contains
+primitive assertions belonging to only one namespace</p>
+<pre> <wsp:Policy> <wsp:Policy> <wsp:Policy>
+ <wsp:Policy>
+ <a:Foo/> <a:Foo/> <b:Foo/> <c:Bar/>
+ <a:Bar/> => <a:Bar/> </wsp:Policy>
+ </wsp:Policy>
+ <b:Foo/> </wsp:Policy>
+ <c:Bar/>
+ </wsp:Policy></pre>
+
+<p>Then each policy is given to the appropriate PolicyExtension with an</p>
+
+<p>org.w3c.Element type object to which the module can append any other
+elements/attributes it wishes. Those attributes/elements should resolved to
+meaningful stub functions via PolicyExtensionTemplate.xsl at latter point of
+time.</p>
+
+<p>For instance depending on the policy, Security module can append
+<username>, <passwd> elements to the given element as children,
+which are later resolved into setUsername(..), setPasswd(..), functions of
+the stub. This way a module can add additional methods to the stub which can
+be used get specific parameters to the module. Those methods store any user
+input in the ServiceClient properties</p>
+
+<p>(ServiceClient.getOptions().putProperty(...)) which can later be access by
+the module.</p>
+
+<h4>Phase2: At MultiLanguageClientEmitter</h4>
+
+<p>Further, effective policies (based on the WSDL) at appropriate levels</p>
+
+<p>(service level, operation level) are stored as policy strings in the stub.
+Few more generic methods are also added to the stub which are used to
+evaluate/processing policies at runtime.</p>
+
+<h4>Phase3: Runtime</h4>
+
+<p>When a new stub object is created, the policy strings in the stub are</p>
+
+<p>converted into policy objects and merge together to get the effective</p>
+
+<p>policies of each operation. That policy information is stored in the</p>
+
+<p>AxisOperation object which a module can access at later point of time.</p>
+
+<p></p>
+
+<p>Then based on its policy each AxisOperation is engaged to a set of
+modules.</p>
+
+<p></p>
+
+<p>And when the stub method is invoked, those modules which are engaged to</p>
+
+<p>that AxisOperation, access the policy information for that operation
+via</p>
+
+<p>AxisOperation object. It can get other information needed from the</p>
+
+<p>MessageContext which are get stored by stub methods which the module
+has</p>
+
+<p>added to the stub earlier. The modules are required to loads their
+configurations according to that policy information and properties they get
+via MessageContext.</p>
+
+<p></p>
+
+<p></p>
+
+<p>Server side:</p>
+
+<h2>What's in this release?</h2>
+
+<p>In this current release Axis2 framework uses ws-commons/policy as an
+object model to manipulate policy documents. All its description builders
+store any policy information included in description documents (services.xml,
+axis2.xml, .. etc) in the appropriate description classes. This information
+is available at both deployment and run time via these description
+classes.</p>
+
+<p>When generating WSDL dynamically for each service, policy information in
+the description classes is included. For instance, if you declare a policy in
+axis2.xml then that policy is reflected in service elements of WSDL of every
+service. If a policy is declared in a services.xml, it is shown in the
+service element of WSDL for that particular service.</p>
+
+<p>Next step is to use that information to engage and configure required
+modules and allow the module to make use of this policy information.</p>
+
+<p>It is evident that a great deal of work is required to make axis2 a fully
+fledged ws-policy supported web service infrastructure. But it is encouraging
+to note that we've taken the first steps towards this goal. We appreciate any
+suggestions, patches etc you send us in this regard. Keep on
+contributing...!</p>
+</body>
+</html>
Modified: webservices/axis2/trunk/java/xdocs/latest/userguide1.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/userguide1.html?rev=384737&r1=384736&r2=384737&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/userguide1.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/userguide1.html Fri Mar 10 01:09:36 2006
@@ -163,7 +163,7 @@
<h4><a name="Experimental_Features_List">Experimental Features List</a></h4>
<ol type="1">
<li>Sessions scoping for Application, SOAP, Transport and Request levels</li>
- <li>Server side <a href="WS_policy.html" target="_blank">Web Service Policy</a> support</li>
+ <li><a href="WS_policy.html" target="_blank">Server side & client side Web Service Policy support</a></li>
<li>?wsdl and ?xsd support</li>
<li>Generating ServiceClient for a given WSDL and invoke the corresponding service using generated client.</li>
</ol>