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 2006/05/03 13:53:30 UTC
svn commit: r399272 - /webservices/axis2/trunk/java/xdocs/index.html
Author: deepal
Date: Wed May 3 04:53:29 2006
New Revision: 399272
URL: http://svn.apache.org/viewcvs?rev=399272&view=rev
Log:
small fixing
Modified:
webservices/axis2/trunk/java/xdocs/index.html
Modified: webservices/axis2/trunk/java/xdocs/index.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/index.html?rev=399272&r1=399271&r2=399272&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/index.html Wed May 3 04:53:29 2006
@@ -1,371 +1,367 @@
-<html>
-<head>
- <meta http-equiv="content-type" content="">
- <title>Apache Axis2 - Next Generation Web Services</title>
- <style type="text/css">
-<!--
-.style1 {
-font-size: 24px;
-font-weight: bold;
-color: #FF0000;
-}
--->
-
-
-
-
-
-
-
-
-
-
-
- </style>
-</head>
-
-<body lang="en">
-<h2>Welcome to Apache Axis2</h2>
-
-<p>Apache Axis2 is an implementation of the <a
-href="http://www.w3.org/TR/soap/">Simple Object Access Protocol (SOAP)
-Recommendation</a> from the <a href="http://www.w3.org">W3C</a>. Axis2 can
-be used to provide and consume Web Services.</p>
-
-<p>From the <a href="http://www.w3.org/TR/soap/">W3C recommendation</a>:</p>
-
-<div style="padding-left: 20px; padding-top: 5px; font-style:italic;">
-"SOAP is a lightweight protocol for exchange of 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 data types, and a convention for
-representing remote procedure calls and responses."</div>
-
-<p>Apache Axis2 is an effort to re-implement both Axis/Java and Axis/C++ on a
-new architecture. Building upon the "handler chain" model developed in Axis1,
-Axis2 introduces a more flexible pipeline architecture which leads itself to
-greater modularity and extensibility. This extensibility will allow Axis2 to
-act as a foundation for a growing constellation of associated Web Services
-protocols including:</p>
-<ul>
- <li><a
- 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"
- target="_blank">WS-Security</a></li>
- <li><a href="http://www.w3.org/Submission/ws-addressing/"
- target="_blank">WS-Addressing</a></li>
-</ul>
-
-<h2>Latest Release</h2>
-
-<h3>04 May 2006 - Apache Axis2 Version 1.0 Released!</h3>
-<!--<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.95</a>)</p>-->
-
-<p>This release includes the following features:</p>
-
-<h4 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Axis2 Completed
-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
- infoset support.</li>
- <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
- (In-Out).</li>
- <li>Module Architecture, mechanism to extend the SOAP Processing model.</li>
- <li>Module version support, can have multiple versions of the same module
- and use them depending on the requirement.</li>
- <li>Context hierarchy</li>
- <li>Archive based deployment model and Directory based deployment model</li>
- <li>JWS like deployment (making Java class into Web service)</li>
- <li>WSDL Code Generation tool for stubs and skeletons</li>
- <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
- versions</li>
- <li>WSS4J module for security (Apache Rampart)</li>
- <li>Improved and user friendly Client API</li>
- <li>WSDL2Java and Java2WSDL</li>
- <li>REST (REpresentational State Transfer) Support</li>
- <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
- <li>Raw XML and RPC providers</li>
- <li>Support for MTOM/ MIME/ SwA</li>
- <li>SAAJ implementation</li>
- <li>DOOM (OM DOM implementation)</li>
- <li>Pack/Unpack capability for the generated code</li>
- <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
- <li>Transport framework improvements (ListenerManager)</li>
- <li>Module disengagemnt support</li>
- <li>Loading modules (.mar files) from classpath</li>
- <li>Sessions scoping for Application, SOAP, Transport and Request
- levels</li>
- <li>Server side and client side Web service Policy support</li>
- <li>?wsdl and ?xsd support</li>
- <li>Dynamic ServiceClient generation for a given WSDL and invoking the
- corresponding service using generated client</li>
- <li>WSDL fault handling (fault code generation)</li>
- <li>SOAP 1.1 & 1.2 and HTTP binding generation (?wsdl)</li>
- <li>Streaming Attachments support for MTOM (SOAP Message Transmission
- Optimization Mechanism)</li>
-</ol>
-
-<h4>Experimental Features List</h4>
-<ol type="1">
- <li>URL based deployment mechanism (starting Axis with remote
- repository)</li>
- <li>Unexpanded war support (location of axis2.xml and repository can be
- specified in web.xml )</li>
-</ol>
-
-<h3>What's Still To Do?</h3>
-
-<p>See list of what we think needs to be done, and consider helping out if
-you're interested and able!</p>
-<ol type="1">
- <li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
- <li>SOAP Encoding</li>
- <li>Binary serialization and de-serialization support</li>
- <li>Resource framework implementation (WS-RF) and Enterprise web services
- such as JSR 109 support</li>
- <li>HTTP transport based on URL.openConnection (to be usable in Java Web
- Start clients, because of authenticating proxies)</li>
-</ol>
-
-<h2>Axis2 Background and Motivation</h2>
-
-<p>Axis1 was built under the assumption that other protocols such as
-WS-ReliableMessaging would be integrated into Axis1's handler chain. Axis1
-had the concept of a <a
-href="http://ws.apache.org/axis/java/apiDocs/org/apache/axis/MessageContext.html">MessageContext</a>
-and a chain of transport, service, and global message handlers, but Axis1
-lacked a clear extension architecture to enable clean composition of such
-layers. One of the key motivations for Axis2 is to provide a clean and simple
-environment for implementations of associated WS standards such as <a
-href="http://ws.apache.org/sandesha/">Apache Sandesha</a> and <a
-href="http://ws.apache.org/wss4j/">Apache WSS4J</a>. Implementations of
-associated standards should be able to easily interface with the base SOAP
-Message handling system. In summary, Axis2 has a more modular and flexible
-message handling pipeline. It focuses on the details of message handling and
-provides clear hooks for implementations of associated Web Services standards
-and protocols. This evolution will allow Axis to be a foundational technology
-for next generation Web Services.</p>
-
-<p>Axis2 introduces a representation for SOAP messages called <b>AXIOM (AXIs
-Object Model)</b>. AXIOM consists of two parts: a complete XML Infoset
-representation and a SOAP Infoset representation. The XML Infoset
-representation provides a JDOM-esque API built on top a deferred model via a
-StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM
-is that it allows one to stop building the XML tree and just access the pull
-stream directly, enabling both maximum flexibility and maximum performance.
-This approach allows Axis2 to support multiple levels of abstraction for
-consuming and offering Web services using plain AXIOM, or using generated
-code and statically data-bound data types and so on. Developers with
-demanding performance requirements will be able to use AXIOM to create highly
-scalable Web Services.</p>
-
-<p>A third shift in Axis 2 is the de-emphasis of RPC-oriented Web Services
-and a shift towards more document-oriented message style asynchronous service
-interactions. With Axis2 clients can interact with servers in a number of
-ways, and the client API provides both a blocking and non-blocking API. At
-the time of Axis1's design, RPC-style, synchronous, request-response
-interactions were the order of the day for Web services. Today service
-interactions are much more message-oriented and exploit many different
-message exchange patterns. The Axis2 engine architecture is careful not to
-build in any assumptions of request-response patterns to ensure that it can
-be used easily to support arbitrary message exchange patterns. Don't worry,
-you'll still be able to use Axis2 like you used Axis1. One just have a richer
-set of options for client-server interaction.</p>
-
-<h2>Archived News</h2>
-
-<h3>23 March 2006 - Apache Axis2 Version 0.95 Released!</h3>
-
-<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.95</a>)</p>
-
-<p>This release includes the following features:</p>
-
-<h4 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Axis2 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
- infoset support.</li>
- <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
- (In-Out)</li>
- <li>Module Architecture, mechanism to extend the SOAP Processing Model</li>
- <li>Module version support , can have multiple versions of the same module
- and use them depending on the requirement.</li>
- <li>Content hierarchy</li>
- <li>Archive based deployment Model and Directory based deployment model</li>
- <li>JWS like deployment (making Java class into Web service)</li>
- <li>WSDL Code Generation Tool for Stub and skeletons</li>
- <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
- versions</li>
- <li>WSS4J module for security</li>
- <li>Improved and user friendly Client API</li>
- <li>WSDL2Java and Java2WSDL</li>
- <li>REST (REpresentational State Transfer) Support</li>
- <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
- <li>Raw XML providers</li>
- <li>Support for MTOM/ MIME/ SwA</li>
- <li>SAAJ implementation</li>
- <li>DOOM</li>
- <li>Pack/Unpack capability for the generated code</li>
- <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
- <li>Numerous bug fixes since last release</li>
- <li>Transport framework improvements (ListenerManager)-<span
- style="color: #FF0000">New</span></li>
- <li>AxisServlet auto start when application server get start up-<span
- style="color: #FF0000">New</span></li>
- <li>Module dis-engagemnt support-<span
- style="color: #FF0000">New</span></li>
- <li>Loading module (.mar) from classpath-<span
- style="color: #FF0000">New</span></li>
- <li>Sessions scoping for Application, SOAP, Transport and Request
- levels-<span style="color: #FF0000">New</span></li>
-</ol>
-
-<p id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad"><strong><em>Axis2
-Experimental Features List</em></strong></p>
-<ol type="1">
- <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>
-
-<h4 id="head-7dd8e783bb9e22fb00f88748855bb6e500111e12">Major Changes Since
-Last Release</h4>
-<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>
- <pre> <actionMapping>MyMapping</actionMapping>
- </pre>
- <li>Refactored following packages in Axiom.
- <ul>
- <li>org.apache.axiom.om.impl.llom.builder to
- org.apache.axiom.om.impl.builder</li>
- <li>org.apache.axiom.om.impl.llom.mtom to
- org.apache.axiom.om.impl.mtom</li>
- <li>org.apache.axiom.om.impl.llom.serialize to
- org.apache.axiom.om.impl.serialize</li>
- <li>org.apache.axiom.om.impl.llom.traverse to
- org.apache.axiom.om.impl.traverse</li>
- </ul>
- </li>
-</ol>
-
-<h4 id="head-83371cc3d6961295be042f584c7b74d81cca23c4">Tools Included In This
-Release</h4>
-<ol type="1">
- <li>Axis2 Web Application (Web App)</li>
- <li>WSDL2WS- Command line version</li>
- <!--<li>Service Archive Wizard- eclipse Plugin</li>-->
-</ol>
-
-<h4 id="head-599c5a50552f02ebdeb5f58ef8da289234812ca4">What's Still To
-Do?</h4>
-
-<p>See list of what we think needs to be done, and consider helping out if
-you're interested & able!</p>
-<ol type="1">
- <li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
- <li>SOAP Encoding</li>
- <li>Binary serialization and de-serialization support</li>
- <li>Management Interface for Axis2</li>
- <li>Implementation of other Transports.</li>
- <li>Resource framework implementation (WS-RF) and Enterprise web services
- such as JSR 109 support</li>
- <li>Completion of Interop tests</li>
-</ol>
-
-<h3>11 January 2006 - Apache Axis2 Version 0.94 Released!</h3>
-
-<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.94</a>)</p>
-
-<p>This release includes the following features:</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
- infoset support.</li>
- <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
- (In-Out)</li>
- <li>Module Architecture, mechanism to extend the SOAP Processing Model</li>
- <li>Module version support , can have multiple versions of the same module
- and use them depending on the requirement.</li>
- <li>Content hierarchy</li>
- <li>Archive based deployment Model and Directory based deployment model</li>
- <li>JWS like deployment (making Java class into Web service)</li>
- <li>WSDL Code Generation Tool for Stub and skeletons</li>
- <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
- versions</li>
- <li>WSS4J module for security</li>
- <li>Improved and user friendly Client API</li>
- <li>WSDL2Java</li>
- <li>REST (REpresentational State Transfer) Support</li>
- <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
- <li>Raw XML providers</li>
- <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>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
- <li>Numerous bug fixes since last release</li>
-</ol>
-
-<p id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad"><b>Axis2 Experimental
-Features List</b></p>
-<ol type="1">
- <li>Sessions scoping for Application, SOAP, Transport and Request
- levels</li>
- <li>Server side Web Service Policy support</li>
- <li>?wsdl and ?xsd support</li>
- <li>Java2WSDL</li>
- <li>Generating ServiceClient for a given WSDL and invoke the corresponding
- service using generated client.</li>
-</ol>
-
-<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,
- InOnlyMEPClient, InOutMEPClient, Call. (Please note that the above
- classes will be deprecated in this release.)</li>
- <li>Module versioning support , can have multiple versions of the same
- module and use them depending on the requirement.</li>
- <li>Code generator improved to process multi-port WSDL's properly</li>
- <li>Packing and unpacking options for the code generated classes</li>
-</ol>
-
-<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>
-
-<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>
- <li>Binary serialization and de-serialization support</li>
- <li>Management Interface for Axis2</li>
- <li>Implementation of other Transports.</li>
- <li>Resource framework implementation (WS-RF) and Enterprise web services
- such as JSR 109 support</li>
- <li>Completion of interop tests</li>
-</ol>
-
-<p align="right"><a href="archived_news.html" target="_blank">See more
-Archived News >></a></p>
-</body>
-</html>
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title>Apache Axis2 - Next Generation Web Services</title>
+ <style type="text/css">
+<!--
+.style1 {
+font-size: 24px;
+font-weight: bold;
+color: #FF0000;
+}
+-->
+
+
+
+
+
+
+
+
+
+
+
+ </style>
+</head>
+
+<body lang="en">
+<h2>Welcome to Apache Axis2</h2>
+
+<p>Apache Axis2 is an implementation of the <a
+href="http://www.w3.org/TR/soap/">Simple Object Access Protocol (SOAP)
+Recommendation</a> from the <a href="http://www.w3.org">W3C</a>. Axis2 can
+be used to provide and consume Web Services.</p>
+
+<p>From the <a href="http://www.w3.org/TR/soap/">W3C recommendation</a>:</p>
+
+<div style="padding-left: 20px; padding-top: 5px; font-style:italic;">
+"SOAP is a lightweight protocol for exchange of 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 data types, and a convention for
+representing remote procedure calls and responses."</div>
+
+<p>Apache Axis2 is an effort to re-implement both Axis/Java and Axis/C++ on a
+new architecture. Building upon the "handler chain" model developed in Axis1,
+Axis2 introduces a more flexible pipeline architecture which leads itself to
+greater modularity and extensibility. This extensibility will allow Axis2 to
+act as a foundation for a growing constellation of associated Web Services
+protocols including:</p>
+<ul>
+ <li><a
+ 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"
+ target="_blank">WS-Security</a></li>
+ <li><a href="http://www.w3.org/Submission/ws-addressing/"
+ target="_blank">WS-Addressing</a></li>
+</ul>
+
+<h2>Latest Release</h2>
+
+<h3>04 May 2006 - Apache Axis2 Version 1.0 Released!</h3>
+<!--<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.95</a>)</p>-->
+
+<p>This release includes the following features:</p>
+
+<h4 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Axis2 Completed
+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
+ infoset support.</li>
+ <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
+ (In-Out).</li>
+ <li>Module Architecture, mechanism to extend the SOAP Processing model.</li>
+ <li>Module version support, can have multiple versions of the same module
+ and use them depending on the requirement.</li>
+ <li>Context hierarchy</li>
+ <li>Archive based deployment model and Directory based deployment model</li>
+ <li>JWS like deployment (making Java class into Web service)</li>
+ <li>WSDL Code Generation tool for stubs and skeletons</li>
+ <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
+ versions</li>
+ <li>WSS4J module for security (Apache Rampart)</li>
+ <li>Improved and user friendly Client API</li>
+ <li>WSDL2Java and Java2WSDL</li>
+ <li>REST (REpresentational State Transfer) Support</li>
+ <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
+ <li>Raw XML and RPC providers</li>
+ <li>Support for MTOM/ MIME/ SwA</li>
+ <li>SAAJ implementation</li>
+ <li>DOOM (OM DOM implementation)</li>
+ <li>Pack/Unpack capability for the generated code</li>
+ <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
+ <li>Transport framework improvements (ListenerManager)</li>
+ <li>Module disengagemnt support</li>
+ <li>Loading modules (.mar files) from classpath</li>
+ <li>Sessions scoping for Application, SOAP, Transport and Request
+ levels</li>
+ <li>Server side and client side Web service Policy support</li>
+ <li>?wsdl and ?xsd support</li>
+ <li>Dynamic ServiceClient generation for a given WSDL and invoking the
+ corresponding service using generated client</li>
+ <li>WSDL fault handling (fault code generation)</li>
+ <li>SOAP 1.1 & 1.2 and HTTP binding generation (?wsdl)</li>
+ <li>Streaming Attachments support for MTOM (SOAP Message Transmission
+ Optimization Mechanism)</li>
+ <li>URL based deployment mechanism (starting Axis with remote
+ repository)</li>
+ <li>Unexpanded war support (location of axis2.xml and repository can be
+ specified in web.xml )</li>
+</ol>
+
+<h3>What's Still To Do?</h3>
+
+<p>See list of what we think needs to be done, and consider helping out if
+you're interested and able!</p>
+<ol type="1">
+ <li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
+ <li>SOAP Encoding</li>
+ <li>Binary serialization and de-serialization support</li>
+ <li>Resource framework implementation (WS-RF) and Enterprise web services
+ such as JSR 109 support</li>
+ <li>HTTP transport based on URL.openConnection (to be usable in Java Web
+ Start clients, because of authenticating proxies)</li>
+</ol>
+
+<h2>Axis2 Background and Motivation</h2>
+
+<p>Axis1 was built under the assumption that other protocols such as
+WS-ReliableMessaging would be integrated into Axis1's handler chain. Axis1
+had the concept of a <a
+href="http://ws.apache.org/axis/java/apiDocs/org/apache/axis/MessageContext.html">MessageContext</a>
+and a chain of transport, service, and global message handlers, but Axis1
+lacked a clear extension architecture to enable clean composition of such
+layers. One of the key motivations for Axis2 is to provide a clean and simple
+environment for implementations of associated WS standards such as <a
+href="http://ws.apache.org/sandesha/">Apache Sandesha</a> and <a
+href="http://ws.apache.org/wss4j/">Apache WSS4J</a>. Implementations of
+associated standards should be able to easily interface with the base SOAP
+Message handling system. In summary, Axis2 has a more modular and flexible
+message handling pipeline. It focuses on the details of message handling and
+provides clear hooks for implementations of associated Web Services standards
+and protocols. This evolution will allow Axis to be a foundational technology
+for next generation Web Services.</p>
+
+<p>Axis2 introduces a representation for SOAP messages called <b>AXIOM (AXIs
+Object Model)</b>. AXIOM consists of two parts: a complete XML Infoset
+representation and a SOAP Infoset representation. The XML Infoset
+representation provides a JDOM-esque API built on top a deferred model via a
+StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM
+is that it allows one to stop building the XML tree and just access the pull
+stream directly, enabling both maximum flexibility and maximum performance.
+This approach allows Axis2 to support multiple levels of abstraction for
+consuming and offering Web services using plain AXIOM, or using generated
+code and statically data-bound data types and so on. Developers with
+demanding performance requirements will be able to use AXIOM to create highly
+scalable Web Services.</p>
+
+<p>A third shift in Axis 2 is the de-emphasis of RPC-oriented Web Services
+and a shift towards more document-oriented message style asynchronous service
+interactions. With Axis2 clients can interact with servers in a number of
+ways, and the client API provides both a blocking and non-blocking API. At
+the time of Axis1's design, RPC-style, synchronous, request-response
+interactions were the order of the day for Web services. Today service
+interactions are much more message-oriented and exploit many different
+message exchange patterns. The Axis2 engine architecture is careful not to
+build in any assumptions of request-response patterns to ensure that it can
+be used easily to support arbitrary message exchange patterns. Don't worry,
+you'll still be able to use Axis2 like you used Axis1. One just have a richer
+set of options for client-server interaction.</p>
+
+<h2>Archived News</h2>
+
+<h3>23 March 2006 - Apache Axis2 Version 0.95 Released!</h3>
+
+<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.95</a>)</p>
+
+<p>This release includes the following features:</p>
+
+<h4 id="head-215f3945a40558f9ad055ed5b6601e8f93706558">Axis2 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
+ infoset support.</li>
+ <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
+ (In-Out)</li>
+ <li>Module Architecture, mechanism to extend the SOAP Processing Model</li>
+ <li>Module version support , can have multiple versions of the same module
+ and use them depending on the requirement.</li>
+ <li>Content hierarchy</li>
+ <li>Archive based deployment Model and Directory based deployment model</li>
+ <li>JWS like deployment (making Java class into Web service)</li>
+ <li>WSDL Code Generation Tool for Stub and skeletons</li>
+ <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
+ versions</li>
+ <li>WSS4J module for security</li>
+ <li>Improved and user friendly Client API</li>
+ <li>WSDL2Java and Java2WSDL</li>
+ <li>REST (REpresentational State Transfer) Support</li>
+ <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
+ <li>Raw XML providers</li>
+ <li>Support for MTOM/ MIME/ SwA</li>
+ <li>SAAJ implementation</li>
+ <li>DOOM</li>
+ <li>Pack/Unpack capability for the generated code</li>
+ <li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
+ <li>Numerous bug fixes since last release</li>
+ <li>Transport framework improvements (ListenerManager)-<span
+ style="color: #FF0000">New</span></li>
+ <li>AxisServlet auto start when application server get start up-<span
+ style="color: #FF0000">New</span></li>
+ <li>Module dis-engagemnt support-<span
+ style="color: #FF0000">New</span></li>
+ <li>Loading module (.mar) from classpath-<span
+ style="color: #FF0000">New</span></li>
+ <li>Sessions scoping for Application, SOAP, Transport and Request
+ levels-<span style="color: #FF0000">New</span></li>
+</ol>
+
+<p id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad"><strong><em>Axis2
+Experimental Features List</em></strong></p>
+<ol type="1">
+ <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>
+
+<h4 id="head-7dd8e783bb9e22fb00f88748855bb6e500111e12">Major Changes Since
+Last Release</h4>
+<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>
+ <pre> <actionMapping>MyMapping</actionMapping>
+ </pre>
+ <li>Refactored following packages in Axiom.
+ <ul>
+ <li>org.apache.axiom.om.impl.llom.builder to
+ org.apache.axiom.om.impl.builder</li>
+ <li>org.apache.axiom.om.impl.llom.mtom to
+ org.apache.axiom.om.impl.mtom</li>
+ <li>org.apache.axiom.om.impl.llom.serialize to
+ org.apache.axiom.om.impl.serialize</li>
+ <li>org.apache.axiom.om.impl.llom.traverse to
+ org.apache.axiom.om.impl.traverse</li>
+ </ul>
+ </li>
+</ol>
+
+<h4 id="head-83371cc3d6961295be042f584c7b74d81cca23c4">Tools Included In This
+Release</h4>
+<ol type="1">
+ <li>Axis2 Web Application (Web App)</li>
+ <li>WSDL2WS- Command line version</li>
+ <!--<li>Service Archive Wizard- eclipse Plugin</li>-->
+</ol>
+
+<h4 id="head-599c5a50552f02ebdeb5f58ef8da289234812ca4">What's Still To
+Do?</h4>
+
+<p>See list of what we think needs to be done, and consider helping out if
+you're interested & able!</p>
+<ol type="1">
+ <li>JAX-RPC 1.1 and/or JAX-WS compliance</li>
+ <li>SOAP Encoding</li>
+ <li>Binary serialization and de-serialization support</li>
+ <li>Management Interface for Axis2</li>
+ <li>Implementation of other Transports.</li>
+ <li>Resource framework implementation (WS-RF) and Enterprise web services
+ such as JSR 109 support</li>
+ <li>Completion of Interop tests</li>
+</ol>
+
+<h3>11 January 2006 - Apache Axis2 Version 0.94 Released!</h3>
+
+<p>(<a href="http://ws.apache.org/axis2/download.cgi">Download 0.94</a>)</p>
+
+<p>This release includes the following features:</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
+ infoset support.</li>
+ <li>Support for One-Way Messaging (In-Only) and Request Response Messaging
+ (In-Out)</li>
+ <li>Module Architecture, mechanism to extend the SOAP Processing Model</li>
+ <li>Module version support , can have multiple versions of the same module
+ and use them depending on the requirement.</li>
+ <li>Content hierarchy</li>
+ <li>Archive based deployment Model and Directory based deployment model</li>
+ <li>JWS like deployment (making Java class into Web service)</li>
+ <li>WSDL Code Generation Tool for Stub and skeletons</li>
+ <li>WS-Addressing, both the submission (2004/08) and final (2005/08)
+ versions</li>
+ <li>WSS4J module for security</li>
+ <li>Improved and user friendly Client API</li>
+ <li>WSDL2Java</li>
+ <li>REST (REpresentational State Transfer) Support</li>
+ <li>Transports supports: HTTP, SMTP, TCP, JMS</li>
+ <li>Raw XML providers</li>
+ <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>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
+ <li>Numerous bug fixes since last release</li>
+</ol>
+
+<p id="head-5bb5aa099717d1d49642f7ae2d63ce5cf94487ad"><b>Axis2 Experimental
+Features List</b></p>
+<ol type="1">
+ <li>Sessions scoping for Application, SOAP, Transport and Request
+ levels</li>
+ <li>Server side Web Service Policy support</li>
+ <li>?wsdl and ?xsd support</li>
+ <li>Java2WSDL</li>
+ <li>Generating ServiceClient for a given WSDL and invoke the corresponding
+ service using generated client.</li>
+</ol>
+
+<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,
+ InOnlyMEPClient, InOutMEPClient, Call. (Please note that the above
+ classes will be deprecated in this release.)</li>
+ <li>Module versioning support , can have multiple versions of the same
+ module and use them depending on the requirement.</li>
+ <li>Code generator improved to process multi-port WSDL's properly</li>
+ <li>Packing and unpacking options for the code generated classes</li>
+</ol>
+
+<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>
+
+<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>
+ <li>Binary serialization and de-serialization support</li>
+ <li>Management Interface for Axis2</li>
+ <li>Implementation of other Transports.</li>
+ <li>Resource framework implementation (WS-RF) and Enterprise web services
+ such as JSR 109 support</li>
+ <li>Completion of interop tests</li>
+</ol>
+
+<p align="right"><a href="archived_news.html" target="_blank">See more
+Archived News >></a></p>
+</body>
+</html>