Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 15178 invoked by uid 500); 14 Sep 2001 21:18:38 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 15164 invoked by uid 500); 14 Sep 2001 21:18:38 -0000 Delivered-To: apmail-xml-axis-cvs@apache.org Date: 14 Sep 2001 21:13:42 -0000 Message-ID: <20010914211342.20401.qmail@icarus.apache.org> From: gdaniels@apache.org To: xml-axis-cvs@apache.org Subject: cvs commit: xml-axis/java/docs user-guide.html X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N gdaniels 01/09/14 14:13:42 Modified: java/docs user-guide.html Log: Beginnings of alpha-2 doc edits - checking in so I can finish this from home later. Revision Changes Path 1.13 +21 -12 xml-axis/java/docs/user-guide.html Index: user-guide.html =================================================================== RCS file: /home/cvs/xml-axis/java/docs/user-guide.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- user-guide.html 2001/08/14 20:01:38 1.12 +++ user-guide.html 2001/09/14 21:13:42 1.13 @@ -17,7 +17,7 @@

Axis User's Guide

-

Alpha 1 Version

+

Alpha 2 Version

Table of Contents

Introduction
Installing Axis
@@ -30,7 +30,7 @@ Glossary

Introduction

Welcome to Axis, the third generation of Apache SOAP! This is the alpha - 1 version, our first publically announced milestone. Please note that Axis + 2 version, our first publically announced milestone. Please note that Axis is a work in progress, and although the basic functionality is there, there are still a lot of unfinished areas and rough edges. That said, we're very psyched about the package so far and would love to get your take on how we can make @@ -82,16 +82,16 @@

  • SOAP 1.1 compliant engine
  • Flexible configuration / deployment system -
  • Support for "drop-in" deployment of SOAP services - (JWS) -
  • Support for all basic types, and a type mapping - system for defining new serializers/deserializers +
  • Support for "drop-in" deployment of SOAP services (JWS) +
  • Support for all basic types, and a type mapping system for defining new + serializers/deserializers
  • Automatic serialization/deserialization of Java Beans - -
  • Automatic two-way conversions between Java "List" - collections and SOAP Arrays +
  • Automatic two-way conversions between Java "List" collections and SOAP Arrays
  • Providers for RPC and message based SOAP services -
  • Preliminary security extensions +
  • Automatic WSDL generation from deployed services +
  • Wsdl2java tool for building Java proxies and skeletons from WSDL documents +
  • Preliminary security extensions, which can integrate with Servlet 2.2 security/roles +
  • An EJB provider for accessing EJB's as Web Services
  • HTTP servlet-based transport
  • Standalone version of the server (with HTTP support)
  • Examples, including a client and server for the soapbuilders community interoperability @@ -101,9 +101,8 @@
    • Support for the SOAP with Attachments specification
    • Supprt for multi-dimensional arrays -
    • Support for the SOAP actor attribute +
    • Support for the SOAP actor attribute
    • A final deployment descriptor syntax (WSDD)
      • -
    • WSDL tooling

    All of these items are on the list for the final release.

    Installing Axis and Using this Guide

    @@ -437,6 +436,16 @@ For now, take a look at the ArraySerializer, the BeanSerializer (both in org.apache.axis.encoding), and the DataSer example (in samples/encoding) to see how custom serializers work.

    +

    Using WSDL with Axis

    +

    The Web Service Description Language is a specification authored by IBM and + Microsoft, and supported by many other organizations. WSDL serves to describe + Web Services in a structured way.

    +

    Axis supports WSDL in two ways: first, when you deploy a service in Axis, users + may then access your service's URL with a standard web browser and by appending + "?WSDL" to the end of the URL, they will obtain an automatically-generated + WSDL document which describes your service. Second,

    +

    +

     

    Deployment Reference

    Note: this reference reflects the state of the deploy.xml structure as of the alpha 1 release. This will very likely change in a subsequent release to