1.9 +52 -67 ws-axis/site/src/documentation/content/xdocs/java/user-guide.ihtml Index: user-guide.ihtml =================================================================== RCS file: /home/cvs/ws-axis/site/src/documentation/content/xdocs/java/user-guide.ihtml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- user-guide.ihtml 20 Oct 2004 03:15:04 -0000 1.8 +++ user-guide.ihtml 22 Oct 2004 10:49:15 -0000 1.9 @@ -18,7 +18,7 @@

Axis User's Guide

1.1 Version
+

1.2 Version
Feedback: axis-dev@ws.apache.org

@@ -71,15 +71,11 @@

SOAP is an XML-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, SOAP 1.1, is fast growing in - popularity and usage. The W3C's XML Protocol working group - is in the process of turning SOAP into a true open standard, and - as of this writing has released a working draft of SOAP 1.2, - which cleans up some of the more confusing areas of the 1.1 - spec.

+ conceived by Microsoft and Userland software, it has + evolved through several generations; the current spec is version, + SOAP 1.2, though version 1.1 + is more widespread. The W3C's + XML Protocol working group is in charge of the specification.

SOAP is widely viewed as the backbone to a new generation of cross-platform cross-language distributed computing applications, @@ -244,26 +240,26 @@

Before running the examples in this guide, you'll need to make sure that your CLASSPATH includes (Note: If you build Axis from a CVS checkout, these will be in xml-axis/java/build/lib instead of - axis-1_1/lib):

+ axis-1_2/lib):

axis-1_1/lib/axis.jar
axis-1_2/lib/axis.jar
axis-1_1/lib/jaxrpc.jar
axis-1_2/lib/jaxrpc.jar
axis-1_1/lib/saaj.jar
axis-1_2/lib/saaj.jar
axis-1_1/lib/commons-logging.jar
axis-1_2/lib/commons-logging.jar
axis-1_1/lib/commons-discovery.jar
axis-1_2/lib/commons-discovery.jar
axis-1_1/lib/wsdl4j.jar
axis-1_2/lib/wsdl4j.jar
axis-1_1/ (for the sample - code)
axis-1_2/ (for the sample code)
A JAXP-1.1 compliant XML parser such as Xerces or - Crimson
A JAXP-1.1 compliant XML parser such as Xerces or Crimson. We recommend + Xerces, as it is the one + that the product has been tested against.

@@ -274,34 +270,31 @@

Let's take a look at an example Web Service client that will call the echoString method on the public Axis server at Apache.

  -1  import org.apache.axis.client.Call;
  -2  import org.apache.axis.client.Service;
  -3  import javax.xml.namespace.QName;
  -4  
  -5  public class TestClient {
  -6   public static void main(String [] args) {
  -7 try {
  -8  String endpoint =
  -9   "http://nagoya.apache.org:5049/axis/services/echo";
  -10 
  -11 Service  service = new Service();
  -12 Call  call = (Call) service.createCall();
  -13 
  -14 call.setTargetEndpointAddress( new java.net.URL(endpoint) );
  -15 call.setOperationName(new QName("http://soapinterop.org/", "echoString"));
  -16 
  -17 String ret = (String) call.invoke( new Object[] { "Hello!" } );
  +1   import org.apache.axis.client.Call;
  +2   import org.apache.axis.client.Service;
  +3   import javax.xml.namespace.QName;
  +4   
  +5   public class TestClient {
  +6      public static void main(String [] args) {
  +7          try {
  +8              String endpoint =
  +9                       "http://nagoya.apache.org:5049/axis/services/echo";
  +10  
  +11             Service  service = new Service();
  +12             Call     call    = (Call) service.createCall();
  +13  
  +14             call.setTargetEndpointAddress( new java.net.URL(endpoint) );
  +15             call.setOperationName(new QName("http://soapinterop.org/", echoString"));
  +16  
  +17             String ret = (String) call.invoke( new Object[] { "Hello!" } );
   18  
  -19 System.out.println("Sent 'Hello!', got '" + ret + "'");
  -20   } catch (Exception e) {
  -21 System.err.println(e.toString());
  -22   }
  -23  }
  -24 }
  -
  +19             System.out.println("Sent 'Hello!', got '" + ret + "'");
  +20         } catch (Exception e) {
  +21             System.err.println(e.toString());
  +22         }
  +23     }
  +24  }

(You'll find this file in samples/userguide/example1/TestClient.java)

@@ -638,7 +631,7 @@

If you want to prove to yourself that the deployment really worked, try undeploying the service and calling it again. There's an "undeploy.wsdd" file in the example3/ directory which - you can use just as you did the deploy.wsdd file above. Run the + you can use just as you did the deploy.wsdd file above. Run the AdminClient on that file, then try the service Client again and see what happens.

@@ -1073,20 +1066,6 @@

What Axis can send via SOAP with restricted Interoperability

Unsigned data

- -

You cannot consume or generate services that use unsigned - datatypes with pure JAX-RPC, because there are no unsigned - dataypes in Java.

- -

Axis does have support for the unsigned types, so you can - consume services written in C++, C# and the like, and - re-implement interfaces designed for those languages. Be very - wary about exporting unsigned datatypes, however, as to do so - will stop Java clients that do not use Axis or another SOAP - client library with unsigned support from using them. The current - JAX-RPC specification does not address this issue.

Java Collections

Some of the Collection classes, such as Hashtable, do @@ -1110,8 +1089,11 @@ any class that follows the JavaBean pattern of accessor and mutator. To serve up objects you must either register your classes with this BeanSerializer, or there must be serialization - support built in to Axis. Remote References Remote references are - neither part of the SOAP specification, nor the JAX-RPC + support built in to Axis.

+ +

Remote References

+ +

Remote references are neither part of the SOAP specification, nor the JAX-RPC specification. You cannot return some object reference and expect the caller to be able to use it as an endpoint for SOAP calls or as a parameter in other calls. Instead you must use some other @@ -2319,8 +2301,11 @@

The port used by the SOAP monitor service to comminicate with applets is configurable. Edit the web.xml file for the Axis web - application to change the port to be used. Note: The SOAP - Monitor is NOT enabled by default for security reasons.

+ application to change the port to be used.
+ + Note: The SOAP Monitor is NOT enabled by default for security reasons. + To enable it, read Enabling the + SOAP Monitor in the Installation instructions.

adminPassword
axis.disableServiceList	Flag to disable the list of services feature. Set to false by + default, which enables the list of services by the AxisServlet when a GET + request is performed on the servlet root.
axis.Compiler	Set this flag to hand authentication off to the servlet container.

Axis Architecture Guide

Deserialization

Guide to building Axis

Documentation

Axis System Integration Guide

Axis Reference Guide

-P, --password <argument>

-c, --implementationClassName <argument>

Java2WSDL Reference

Deployment (WSDD) Reference

Global Axis Configuration

Axis Developer's Guide

Installing and deploying web applications using - xml-axis

Axis installation instructions

Step 2: Setting up the libraries

Step 3: starting the web server

Step 5: Installing new Web Services

Classpath setup

Classpath setup

What if it doesn't work?

Summary

Appendix: Enabling the SOAP Monitor

Axis User's Guide

What Axis can send via SOAP with restricted Interoperability

Unsigned data

Java Collections

Remote References

Glossary