ws-axis-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r189921 - in /webservices/axis/trunk/java/xdocs: images/new.gif index.html navigation.xml
Date Fri, 10 Jun 2005 07:59:55 GMT
Author: chinthaka
Date: Fri Jun 10 00:59:53 2005
New Revision: 189921

Adding news stuff to the index.html itself

    webservices/axis/trunk/java/xdocs/images/new.gif   (with props)

Added: webservices/axis/trunk/java/xdocs/images/new.gif
Binary file - no diff available.

Propchange: webservices/axis/trunk/java/xdocs/images/new.gif
    svn:mime-type = application/octet-stream

Added: webservices/axis/trunk/java/xdocs/index.html
--- webservices/axis/trunk/java/xdocs/index.html (added)
+++ webservices/axis/trunk/java/xdocs/index.html Fri Jun 10 00:59:53 2005
@@ -0,0 +1,9 @@
+<title>:: Welcome ::</title><h2>News</h2>
+  <li>07-06-2005 : M2 Released. [<a href="releases.html#M2">Download</a>]
<img src="images/new.gif" width="35" height="10"></li>
+  <li>24-02-2005 : M1 Released. [<a href="releases.html#M1">Download</a>]
+<p align="justify">Axis2 is an effort to re-design and totally re-implement both Axis/Java
and (eventually) Axis/C++ on a new architecture. Evolving from the now standard &quot;handler
chain&quot; model which Axis1 pioneered, Axis2 is developing a more flexible pipeline
architecture which can yet be managed and packaged in a more organized manner. This new design
acknowledges the maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging,
WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time Axis1
was designed, while it was fully expected that other protocols such as WS-ReliableMessaging
would be built on top of it, there was not a proper extension architecture defined to enable
clean composition of such layers. Thus, one of the key motivations for Axis2 is to provide
a clean and simple environment for like Apache Sandesha and Apache WSS4J to layer on top of
the base SOAP system. Another driving force for Axis2 as well as the move away from RPC oriented
Web services towards more document-oriented, message style asynchronous service interactions.
The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs
Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP
Infoset representation on top of that. The XML Infoset representation provides a JDOM-like
simple API but is built on 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; thus enabling both maximum flexibility and maximum performance.
This approach allows us to support multiple levels of abstraction for consuming and offering
Web services: using plain AXIOM, using generated code and statically data-bound data types
and so on. 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
to not build in any assumptions of request-response patterns to ensure that it can be used
easily to support arbitrary message exchange patterns.</p>

Modified: webservices/axis/trunk/java/xdocs/navigation.xml
--- webservices/axis/trunk/java/xdocs/navigation.xml (original)
+++ webservices/axis/trunk/java/xdocs/navigation.xml Fri Jun 10 00:59:53 2005
@@ -5,8 +5,7 @@
     <menu name="Axis 2.0">
        <item name="Home" href="index.html"/> 
-       <item name="News" href="news.html"/>   
-      <item name="Get Invloved" href="svn.html">
+       <item name="Get Invloved" href="svn.html">
       	<item name="Overview" href="overview.html"/>
       	<item name="Setting Up" href="svn.html"/>
       	<item name="Guide Lines" href="guidelines.html"/>

View raw message