axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rineh...@apache.org
Subject cvs commit: xml-axis/java/docs user-guide.html
Date Mon, 10 Dec 2001 21:17:24 GMT
rineholt    01/12/10 13:17:24

  Modified:    java     Tag: alpha-3 release-notes.html
               java/docs Tag: alpha-3 user-guide.html
  Log:
  Just modification to documentation to hopefully closer reflect alpha3 release.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.4.2.1   +8 -16     xml-axis/java/release-notes.html
  
  Index: release-notes.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/release-notes.html,v
  retrieving revision 1.4
  retrieving revision 1.4.2.1
  diff -u -r1.4 -r1.4.2.1
  --- release-notes.html	2001/09/21 15:48:38	1.4
  +++ release-notes.html	2001/12/10 21:17:24	1.4.2.1
  @@ -14,9 +14,9 @@
   </style>
   </head>
   <body>
  -<h2>Axis Alpha 2 Release Notes</h2>
  +<h2>Axis Alpha 3 Release Notes</h2>
   
  -<p>This is the <a href="http://xml.apache.org/axis/releases.html"> alpha 2
release</a> 
  +<p>This is the <a href="http://xml.apache.org/axis/releases.html"> alpha 3
release</a> 
     of the <a href="http://xml.apache.org/axis"> Axis SOAP library</a>. (Wondering

     what Axis is? Please see our <a href="http://xml.apache.org/axis/faq.html">FAQ</a>.)</p>
   <h3>General Alpha Information</h3>
  @@ -25,8 +25,6 @@
   missing features include:</p>
   
   <ul>
  -<li>No support for SOAP attachments
  -<li>Deployment syntax not finalized
   <li>Incomplete Apache SOAP 2.2 deployment descriptor support
   <li>Minimal testing in EJB / application server frameworks
     <li>No support for XML-RPC, SMTP 
  @@ -55,19 +53,13 @@
     release. Progress towards that beta release may be viewed on Axis's <a href="http://xml.apache.org/axis/requirements.html">

     requirements and status page</a>.</p>
   <h3>What's New?</h3>
  -<p>Changes since alpha-1:</p>
  +<p>Changes since alpha-2:</p>
   <ul>
  -  <li>Added support for auto-generating WSDL from any URL-accessible service (i.e.

  -    JWS services)!</li>
  -  <li>Added a Wsdl2java tool for building Axis stubs and skeletons from WSDL files!</li>
  -  <li>SimpleAxisServer now supports HTTP basic authentication</li>
  -  <li>Revamp authentication handlers to use an extensible &quot;security provider&quot;

  -    interface, which should allow easy integration with existing security providers 
  -    such as those provided by application servers. A basic version and a version 
  -    which uses servlet 2.2 authentication are both provided.</li>
  -  <li>The &quot;org.apache.axis.utils.Debug&quot; class is gone, and we now
use 
  -    <a href="http://jakarta.apache.org/log4j/docs/index.html">log4j</a> as
our 
  -    logging / debugging library.</li>
  +  <li>Added a <a href="docs/user-guide.html#Java2WSDLReference">java2wsdl</a>
tool for building WSDL from Java files!</li>
  +  <li>Many enhancement for the <a href="docs/user-guide.html#WSDL2JavaReference">wsdl2java</a>
JAX-RPC compliant
  +  emitter.</li>
  +  <li>Deployment syntax now finalized using <a href="docs/user-guide.html#DeploymentReference">WSDD</a>
files.</li>
  +  <li>Preliminary support for SOAP with <A href="docs/user-guide.html#AttachmentsReference">attachments</a>.</li>
     <li>Many minor bug fixes.</li>
   </ul>
   </body>
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.28.2.1  +35 -15    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.28
  retrieving revision 1.28.2.1
  diff -u -r1.28 -r1.28.2.1
  --- user-guide.html	2001/12/04 19:47:54	1.28
  +++ user-guide.html	2001/12/10 21:17:24	1.28.2.1
  @@ -27,8 +27,9 @@
     <A href="#PublishingServices">Publishing Web Services with Axis</a><br>
     <A href="#DataMapping">XML &lt;-&gt; Java Data Mapping in Axis<br>
     </a> <A href="#WSDL">Using WSDL with Axis</a><br>
  -  <br>
  +  <A href="#AttachmentsReference">SOAP with Attachments</a><br>
     <A href="#DeploymentReference">Deployment Reference</a><br>
  +  <br>
     <A href="#Glossary">Glossary</a></p>
   <h2><a name="Introduction"></a>Introduction</h2>
   <p>Welcome to Axis, the third generation of Apache SOAP! This is the <b>alpha

  @@ -37,7 +38,7 @@
     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 it better. </p>
   <h3>What is SOAP?</h3>
  -<p>SOAP is an XML<i>-</i>based communitcation protocol and encoding format
for 
  +<p>SOAP is an XML<i>-</i>based communication protocol and encoding format
for 
     inter-application communication. Originally conceived by Microsoft and Userland 
     software, it has evolved through several generations and the current spec, <a href="http://w3.org/TR/soap">SOAP

     1.1</a>, is fast growing in popularity and usage. The W3C's XML Protocol working

  @@ -58,7 +59,7 @@
     result of months of continued discussion and coding effort in this direction. 
     Some of the key Axis features include the following:</p>
   <ul>
  -  <li> <b>Speed.</b> Axis uses SAX (event-based) parsing to acheive significantly

  +  <li> <b>Speed.</b> Axis uses SAX (event-based) parsing to achieve significantly

       greater speed than earlier versions of Apache SOAP. 
     <li><b>Flexibility.</b> The Axis architecture gives the developer complete
freedom 
       to insert extensions into the engine for custom header processing, system 
  @@ -76,7 +77,7 @@
     and lend a hand! The Axis developer community welcomes your participation.</p>
   <h4><b>Let us know what you think!</b></h4>
   <p>Please send feedback about the package to "<A href="mailto:axis-user@xml.apache.org">axis-user@xml.apache.org</a>".

  -  Also, Axis is regsitered in <a href="http://nagoya.apache.org/bugzilla">bugzilla</a>,

  +  Also, Axis is regisitered in <a href="http://nagoya.apache.org/bugzilla">bugzilla</a>,

     the Apache bug tracking and feature-request database.</p>
   <h3>What's in this release?</h3>
   <p>This release includes the following features:</p>
  @@ -100,8 +101,7 @@
   </ul>
   <h3>What's missing?</h3>
   <ul>
  -  <li>Support for the SOAP with Attachments specification 
  -  <li>Supprt for multi-dimensional arrays 
  +  <li>Support for multi-dimensional arrays 
     <li>Support for the SOAP actor attribute 
     <li>Support for generating complex type definitions in WSDL 
   </ul>
  @@ -120,7 +120,7 @@
   <h3>Handlers and the Message Path in Axis</h3>
   <p>Put simply, Axis is all about processing Messages. When the central Axis processing

     logic runs, a series of <b>Handlers</b> are each invoked in order. The particular

  -  oder is determined by two factors - deployment configuration and whether the 
  +  order is determined by two factors - deployment configuration and whether the 
     engine is a client or a server. The object which is passed to each Handler invocation

     is a <b>MessageContext</b>. A MessageContext is a structure which contains
several 
     important parts: 1) a &quot;request&quot; message, 2) a &quot;response&quot;

  @@ -560,13 +560,21 @@
     to the service, the data types it uses, and where the service is located. Please 
     see the spec (follow the link in the first sentence) for details about WSDL's 
     format and options.</p>
  -<p>Axis supports WSDL in two ways: first, when you deploy a service in Axis, users

  +<p>Axis supports WSDL in the following ways:
  +  <ul>
  +   <li>
  +    When you deploy a service in Axis, users 
     may then access your service's URL with a standard web browser and by appending 
     &quot;?WSDL&quot; to the end of the URL, they will obtain an automatically-generated

  -  WSDL document which describes your service. Second, we provide a &quot;Wsdl2java&quot;

  -  tool which will build Java proxies and skeletons for services with WSDL descriptions.

  -  Both of these techniques are explained in more detail below.</p>
  -<h3>WSDL generation for deployed services</h3>
  +  WSDL document which describes your service. </li>
  +  <li>The &quot;<B>Java2wsdl</b>&quot; 
  +  tool which can do a similar generation of WSDL from Java as the previously mentioned
URL mechanisms,
  +  but allows the generation of WSDL prior to deployment and provides much more control
over the WSDL that is generated.</li> 
  +  <li>The &quot;<B>Wsdl2java</b>&quot; 
  +  tool which will build Java proxies and skeletons for services with WSDL descriptions.</li>

  +  </ul>
  +  These techniques are explained in more detail below.</p>
  +<h3>WSDL generation for deployed services></h3>
   <p>When you make a service available using Axis, there is typically a unique URL

     associated with that service. For JWS files, that URL is simply the path to 
     the JWS file itself. For non-JWS services, this is usually the URL &quot;http://&lt;host&gt;/axis/services/&lt;service-name&gt;&quot;.</p>
  @@ -579,7 +587,16 @@
     the WSDL-generation URL to your online partners, and they'll be able to use 
     it to access your service with toolkits like .NET, SOAP::Lite, or any other 
     software which supports using WSDL.</p>
  -<h3>Building stubs and skeletons with Wsdl2java</h3>
  +<h3><a name="Java2WSDLReference">Generating WSDL with <b>java2wsdl</b></a></h3>
  +  The basic invocation form looks like this:</p>
  +<div class="example">
  +  <pre>% org.apache.axis.wsdlgen.Java2Wsdl<i>(Java Class)</i>
  +</pre>
  +</div>
  +
  +<p><i><font color="#ff0000">Work in progress--- more documentation to
come. </font></i></p>
  +
  +<h3><a name="WSDL2JavaReference">Building stubs and skeletons with Wsdl2java</a></h3>
   <p>You'll find the Axis WSDL -&gt; Java tool in &quot;org.apache.axis.wsdl.Wsdl2java&quot;.

     The basic invocation form looks like this:</p>
   <div class="example">
  @@ -771,6 +788,7 @@
   Only generate code for the WSDL document that appears on the command line.&nbsp;
   The default behaviour is to generate files for all WSDL documents, the
   immediate one and all imported ones.
  +<h3> </h3>
   <h2><a name="DeploymentReference"></a>Deployment Reference</h2>
   Note : all the elements referred to in this section are in the WSDD namespace, 
   namely &quot;http://wsdd&quot;. 
  @@ -889,7 +907,7 @@
     <dt><b>RPCDispatcher</b> 
     <dd>The RPCDispatcher is the pivot point for all RPC services. It accepts the 
       following options: <br>
  -    <b><i>className</i></b> = the class of the backend object to
invoke<br>
  +    <b><i>className</i></b> = the class of the back end object
to invoke<br>
       <b><i>methodName</i></b> = a space-separated list of methods
which are exported 
       as web services. The special value &quot;*&quot; matches all public methods

       in the class. 
  @@ -897,7 +915,7 @@
     <dt><b>MsgDispatcher</b> 
     <dd>The MsgDispatcher is the pivot point for all messaging services. It accepts

       the following options: <br>
  -  <dd><b><i>className</i></b> = the class of the backend
object to invoke<br>
  +  <dd><b><i>className</i></b> = the class of the back end
object to invoke<br>
       <b><i>methodName</i></b> = a space-separated list of methods
which are exported 
       as web services. The special value &quot;*&quot; matches all public methods

       in the class. 
  @@ -924,6 +942,8 @@
       <pre>% java org.apache.axis.client.AdminClient -llocal:// list</pre>
     <dt></dt>
   </dl>
  +<h2><a name="AttachmentsReference">SOAP with Attachments</a></h2>
  +<p><i><font color="#ff0000">Work in progress--- a lot more work to be
done.. </font></i></p>
   <a name="tcpmon"></a><h2>Using the Axis TCP Monitor (tcpmon) </h2>
   <p>The included &quot;tcpmon&quot; utility can be found in the org.apache.axis.utils

     package. To run it from the command line:</p>
  
  
  

Mime
View raw message