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 aj...@apache.org on 2005/02/24 04:43:59 UTC

svn commit: r155155 - in webservices/axis/trunk/java: README.txt release-notes.html

Author: ajith
Date: Wed Feb 23 19:43:58 2005
New Revision: 155155

URL: http://svn.apache.org/viewcvs?view=rev&rev=155155
Log:
Updating the release note and the readme

Modified:
    webservices/axis/trunk/java/README.txt
    webservices/axis/trunk/java/release-notes.html

Modified: webservices/axis/trunk/java/README.txt
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/README.txt?view=diff&r1=155154&r2=155155
==============================================================================
--- webservices/axis/trunk/java/README.txt (original)
+++ webservices/axis/trunk/java/README.txt Wed Feb 23 19:43:58 2005
@@ -1,56 +1,56 @@
-======================================================
-Apache Axis2 milestone build  (Feb 22, 2005)
-
-http://ws.apache.org/axis2
-------------------------------------------------------
-
-___________________
-Documentation
-===================
- 
- Documentation can be found in the docs directory of the source or binary distribution
-
-___________________
-Installation
-===================
-
- Axis2 Binary distribution contains axis2.war in the webapps directory, to ease the installation into a Servlet container. 
- The installation in the Servlet container is just a matter of copying the axis2.war to the webapps directory. 
- 
- To verify the installation, go to http://127.0.0.1:8080/axis2/ and click on the the "Validate" link
- 
- To build the axis2.war using source distribution use the following command.
- $ maven war 
-
- 
- 
-___________________
-Deploying
-===================
-
-  To deploy a new Web Service in  Axis2 the following three steps must be performed
-  1) Create the Web Service implementation class, supporting classes and the service.xml file, 
-  2) Archive the class files into a jar with the service.xml file in the META-INF
-  3) Drop the jar file to the $AXIS_HOME/WEB-INF/services directory
-
- To verify the deployment please go to http://127.0.0.1:8080/axis2/ and follow the
- "List of Available services" Link 
-
- For more information please refer to the User Guide
-
-___________________
-Support
-===================
- 
- Any problem with this release can be reported to Axis the 
- mailing list or Jira issue tracker. If you are sending a mail to mailing list make sure 
- to add the [Axis2] prefix to the subject.
-
- 
- Mailing list subscription:
- axis-dev-subscribe@ws.apache.org
-
- Jira:
- http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10611
-
- 
+======================================================
+Apache Axis2 milestone build  (Feb 22, 2005)
+
+http://ws.apache.org/axis/2.0h
+------------------------------------------------------
+
+___________________
+Documentation
+===================
+ 
+ Documentation can be found in the docs directory included with both the source and binary distribution
+
+___________________
+Installation
+===================
+
+ Axis2 Binary distribution contains axis2.war in the webapps directory, to ease the installation into a Servlet container. 
+ The installation in the Servlet container is just a matter of copying the axis2.war to the webapps directory. 
+ 
+ To verify the installation, go to http://127.0.0.1:8080/axis2/ and click on the the "Validate" link
+ 
+ To build the axis2.war using source distribution use the following command.
+ $ maven war 
+
+ 
+ 
+___________________
+Deploying
+===================
+
+  To deploy a new Web Service in  Axis2 the following three steps must be performed
+  1) Create the Web Service implementation class, supporting classes and the service.xml file, 
+  2) Archive the class files into a jar with the service.xml file in the META-INF
+  3) Drop the jar file to the $AXIS_HOME/WEB-INF/services directory
+
+ To verify the deployment please go to http://127.0.0.1:8080/axis2/ and follow the
+ "List of Available services" Link 
+
+ For more information please refer to the User Guide
+
+___________________
+Support
+===================
+ 
+ Any problem with this release can be reported to Axis the 
+ mailing list or Jira issue tracker. If you are sending a mail to mailing list make sure 
+ to add the [Axis2] prefix to the subject.
+
+ 
+ Mailing list subscription:
+ axis-dev-subscribe@ws.apache.org
+
+ Jira:
+ http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10611
+
+ 

Modified: webservices/axis/trunk/java/release-notes.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/release-notes.html?view=diff&r1=155154&r2=155155
==============================================================================
--- webservices/axis/trunk/java/release-notes.html (original)
+++ webservices/axis/trunk/java/release-notes.html Wed Feb 23 19:43:58 2005
@@ -9,9 +9,9 @@
 
 <p>This release includes the following features:</p>
 <ul>
-    <li>AXIOM,a SOAP specific streaming XML infoset model for SOAP 1.1/1.2 Messages</li> 
-    <li>WOM, WSDL 1.1/2.0 Component Model</li> 
-    <li>Handler framework with the support to specific the location of the a Handler in a 
+    <li>AXIOM, a SOAP specific streaming XML infoset model for SOAP 1.1/1.2 Messages</li> 
+    <li>WSDL Object Model built based on the proposed WSDL 2.0 Component Model.</li> 
+    <li>Handler framework with the support to specify the location of the Handler in a 
       specific Phase</li> 
     <li>Support to bundle and enable the Handlers as Modules</li> 
     <li>Support for the Synchronous and Asynchronous IN-OUT messaging over HTTP transport</li> 
@@ -29,7 +29,7 @@
     <li> MTOM attachments support</li> 
     <li> Support for other WSDL MEPs, both synchronously and asynchronously </li> 
     <li> Complete XML infoset support for AXIOM</li> 
-    <li> Implements the other transports. e.g. SMTP, TCP..</li> 
+    <li> Implementation of other transports. e.g. SMTP, TCP..</li> 
     <li> Handler framework with the support to specific the location of the a Handler 
       relative to Phase</li> 
     <li> Extend the modules to act as plug-ins</li>