butek 02/03/09 12:14:02
Modified: java/docs user-guide.html
java/samples/userguide/example5 Client.java
Log:
Round 3 of User's Guide updates.
Revision Changes Path
1.40 +255 -201 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.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- user-guide.html 8 Mar 2002 23:12:56 -0000 1.39
+++ user-guide.html 9 Mar 2002 20:14:02 -0000 1.40
@@ -521,8 +521,7 @@
<b>languageSpecificType</b>.
So in this case, we'd be mapping the "my.java.thingy" class to the XML
QName [someNamespace]:[local].
-<p>Let's take a look at how this works in practice. Go look at the
samples/userguide/example5/BeanService.java
-file. (we won't reproduce it here, it's pretty straightforward) The key
+<p>Let's take a look at how this works in practice. Go look at <a
href="../samples/userguide/example5/BeanService.java">samples/userguide/example5/BeanService.java</a>.
The key
thing to notice is that the argument to the service method is an Order
object. Since Order is not a basic type which Axis understands by default,
trying to run this service without a type mapping will result in a fault
@@ -532,8 +531,8 @@
<pre class="example">% java org.apache.axis.client.AdminClient
-llocal:///AdminService deploy.wsdd
<Admin>Done processing</Admin>
-% java Client -llocal:// -n "Glen"
-Hi, Glen!
+% java samples.userguide.example5.Client -llocal://
+Hi, Glen Daniels!
You seem to have ordered the following:
@@ -573,7 +572,7 @@
class (i.e. my.java.thingy) into XML. The other, <b>deserializer</b>, is
the class name of a Deserializer <i>factory</i> that generates Deserializers
which can be used to unmarshall XML into the correct Java class.
-<p>(the <beanMapping> tag is really just shorthand for a <typeMapping>
+<p>(The <beanMapping> tag is really just shorthand for a <typeMapping>
tag with serializer="org.apache.axis.encoding.BeanSerializer" and
deserializer="org.apache.axis.encoding.BeanSerializer$BeanDeserFactory",
but clearly it can save a lot of typing!)
<h2>
@@ -617,8 +616,8 @@
can give 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>You can also generate WSDL files from existing Java classes (see <a
href="#Java2WSDL: Building WSDL from Java">#Java2WSDL:
-Building WSDL from Java</a> ).
+<p>You can also generate WSDL files from existing Java classes (see <a
href="#Java2WSDL: Building WSDL from Java">Java2WSDL:
+Building WSDL from Java</a> ).
<br>
<h3>
<a NAME="WSDL2Java: Building stubs, skeletons, and data"></a>WSDL2Java:
@@ -628,18 +627,18 @@
Client-side bindings</h4>
You'll find the AXIS WSDL -> Java tool in "org.apache.axis.wsdl.WSDL2Java".
The basic invocation form looks like this:
-<div class="example">
+<div class="example">
<br><font face="Courier New,Courier">% java org.apache.axis.wsdl.WSDL2Java
(WSDL-file-URL)</font></div>
-<p><br>This will generate only those bindings necessary for the client.
+<p>This will generate only those bindings necessary for the client.
AXIS follows the JAX-RPC specification when generating Java client bindings
from WSDL. For this discussion, assume we executed the following:
-<p><font face="Courier New,Courier">% cd samples/addr</font>
-<br><font face="Courier New,Courier">% java org.apache.axis.wsdl.WSDL2Java
-AddressBook.wsdl</font>
+<div class="example"><br><font face="Courier New,Courier">% cd samples/addr
+<br>% java org.apache.axis.wsdl.WSDL2Java
+AddressBook.wsdl</font></div>
<p>The generated files will reside in the directory "AddressFetcher2".
-They are put here because that is the target namespace from the WSDL.
+They are put here because that is the target namespace from the WSDL and namespaces
map to Java packages.
Namespaces will be discussed in detail later.
<br>
<br>
@@ -692,39 +691,26 @@
The Java class generated from a WSDL type will be named from the WSDL type.
This class will typically, though not always, be a bean. For example,
given the WSDL (the WSDL used throughout the WSDL2Java discussion is from
-the Address Book sample):
-<p><font face="Courier New,Courier">
<xsd:complexType
-name="phone"></font>
-<br><font face="Courier New,Courier">
-<xsd:all></font>
-<br><font face="Courier
New,Courier">
-<xsd:element name="areaCode" type="xsd:int"/></font>
-<br><font face="Courier
New,Courier">
-<xsd:element name="exchange" type="xsd:string"/></font>
-<br><font face="Courier
New,Courier">
-<xsd:element name="number" type="xsd:string"/></font>
-<br><font face="Courier New,Courier">
-</xsd:all></font>
-<br><font face="Courier New,Courier">
</xsd:complexType></font>
+the <a href="../samples/addr/AddressBook.wsdl">Address Book sample</a>):
+<div class="example"><br><font face="Courier New,Courier"><xsd:complexType
+name="phone">
+<br> <xsd:all>
+<br> <xsd:element name="areaCode" type="xsd:int"/>
+<br> <xsd:element name="exchange" type="xsd:string"/>
+<br> <xsd:element name="number" type="xsd:string"/>
+<br> </xsd:all>
+<br></xsd:complexType></font></div>
<p>WSDL2Java will generate:
-<p><font face="Courier New,Courier">public class Phone implements
java.io.Serializable
-{</font>
-<br><font face="Courier New,Courier"> public Phone()
-{...}</font>
-<br><font face="Courier New,Courier"> public int getAreaCode()
-{...}</font>
-<br><font face="Courier New,Courier"> public void setAreaCode(int
-areaCode) {...}</font>
-<br><font face="Courier New,Courier"> public java.lang.String
-getExchange() {...}</font>
-<br><font face="Courier New,Courier"> public void
setExchange(java.lang.String
-exchange) {...}</font>
-<br><font face="Courier New,Courier"> public java.lang.String
-getNumber() {...}</font>
-<br><font face="Courier New,Courier"> public void
setNumber(java.lang.String
-number) {...}</font>
-<br><font face="Courier New,Courier">}</font>
-<br>
+<div class="example"><br><font face="Courier New,Courier">public class Phone
implements java.io.Serializable {
+<br> public Phone() {...}
+<br> public int getAreaCode() {...}
+<br> public void setAreaCode(int areaCode) {...}
+<br> public java.lang.String getExchange() {...}
+<br> public void setExchange(java.lang.String exchange) {...}
+<br> public java.lang.String getNumber() {...}
+<br> public void setNumber(java.lang.String number) {...}
+<br>}</font>
+</div>
<h4>
Holders</h4>
This type may be used as an inout or out parameter. Java does not
@@ -732,19 +718,19 @@
behavior, JAX-RPC specifies the use of holder classes. A holder class
is simply a class that contains an instance of its type. For example,
the holder for the Phone class would be:
-<p><font face="Courier New,Courier">public final class PhoneHolder implements
-javax.xml.rpc.holders.Holder {</font>
-<br><font face="Courier New,Courier"> public Phone value;</font>
-<p><font face="Courier New,Courier"> public PhoneHolder()
-{</font>
-<br><font face="Courier New,Courier"> }</font>
-<p><font face="Courier New,Courier"> public PhoneHolder(Phone
-value) {</font>
-<br><font face="Courier New,Courier">
-this.value = value;</font>
-<br><font face="Courier New,Courier"> }</font>
-<br><font face="Courier New,Courier">}</font>
-<p>A holder class is ONLY generated for a type if that type is used as
+<div class="example"><br><font face="Courier New,Courier">public final class
PhoneHolder implements
+javax.xml.rpc.holders.Holder {
+<br> public Phone value;
+<br>
+<br> public PhoneHolder()
+{
+<br> }
+<br>
+<br> public PhoneHolder(Phone value) {
+<br> this.value = value;
+<br> }
+<br>}</font></div>
+<p>A holder class is <b>only</b> generated for a type if that type is used as
an inout or out parameter.
<p>The holder classes for the primitive types can be found in javax.xml.rpc.holders.
<br>
@@ -753,26 +739,23 @@
The Service Definition Interface (SDI) is the interface that's derived
from a WSDL's portType. This is the interface you use to access the
operations on the service. For example, given the WSDL:
-<p><font face="Courier New,Courier"> <message name="empty"></font>
-<br><font face="Courier New,Courier"> <message
name="AddEntryRequest"></font>
-<br><font face="Courier New,Courier"> <part name="name"
-type="xsd:string"/></font>
-<br><font face="Courier New,Courier"> <part name="address"
-type="typens:address"/></font>
-<br><font face="Courier New,Courier"> </message></font>
-<br><font face="Courier New,Courier"> <portType name="AddressBook"></font>
-<br><font face="Courier New,Courier"> <operation
name="addEntry"></font>
-<br><font face="Courier New,Courier"> <input
-message="tns:AddEntryRequest"/></font>
-<br><font face="Courier New,Courier"> <output
-message="tns:empty"/></font>
-<br><font face="Courier New,Courier"> </operation></font>
+<div class="example"><br><font face="Courier New,Courier"><message name="empty">
+<br><message name="AddEntryRequest">
+<br> <part name="name" type="xsd:string"/>
+<br> <part name="address" type="typens:address"/>
+<br></message>
+<br><portType name="AddressBook">
+<br> <operation name="addEntry">
+<br> <input message="tns:AddEntryRequest"/>
+<br> <output message="tns:empty"/>
+<br> </operation>
+<br></portType></font></div>
<p>WSDL2Java will generate:
-<p><font face="Courier New,Courier">public interface AddressBook extends
-java.rmi.Remote {</font>
-<br><font face="Courier New,Courier"> public void addEntry(String
-name, Address address) throws java.rmi.RemoteException;</font>
-<br><font face="Courier New,Courier">}</font>
+<div class="example"><br><font face="Courier New,Courier">public interface
AddressBook extends
+java.rmi.Remote {
+<br> public void addEntry(String
+name, Address address) throws java.rmi.RemoteException;
+<br>}</font></div>
<p>The name of the SDI is typically the name of the portType. However,
if information in the binding affects the appearance of the SDI, then the
name of the SDI is the name of the binding, not the name of the portType.
@@ -792,24 +775,23 @@
which are involved in dynamic invocation via the Service and Call objects.
The stub hides all that work for you.
<p>Given the following WSDL snippet:
-<p><font face="Courier New,Courier"> <binding name="AddressBookSOAPBinding"
-type="tns:AddressBook"></font>
-<br><font face="Courier New,Courier"> ...</font>
-<br><font face="Courier New,Courier"> </binding></font>
+<div class="example"><br><font face="Courier New,Courier"><binding
name="AddressBookSOAPBinding"
+type="tns:AddressBook">
+<br> ...
+<br></binding></font></div>
<p>WSDL2Java will generate:
-<p><font face="Courier New,Courier">public class AddressBookSOAPBindingStub
-extends org.apache.axis.client.Stub implements AddressBook {</font>
-<br><font face="Courier New,Courier"> public
AddressBookSOAPBindingStub()
-throws org.apache.axis.AxisFault {...}</font>
-<br><font face="Courier New,Courier"> public
AddressBookSOAPBindingStub(URL
+<div class="example"><br><font face="Courier New,Courier">public class
AddressBookSOAPBindingStub
+extends org.apache.axis.client.Stub implements AddressBook {
+<br> public AddressBookSOAPBindingStub()
+throws org.apache.axis.AxisFault {...}
+<br> public AddressBookSOAPBindingStub(URL
endpointURL, javax.xml.rpc.Service service) throws org.apache.axis.AxisFault
-{...}</font>
-<br><font face="Courier New,Courier"> public
AddressBookSOAPBindingStub(javax.xml.rpc.Service
-service) throws org.apache.axis.AxisFault {...}</font>
-<br><font face="Courier New,Courier"> public void addEntry(String
-name, Address address) throws RemoteException{...}</font>
-<br><font face="Courier New,Courier">}</font>
-<br>
+{..}
+<br> public AddressBookSOAPBindingStub(javax.xml.rpc.Service
+service) throws org.apache.axis.AxisFault {...}
+<br> public void addEntry(String
+name, Address address) throws RemoteException{...}
+<br>}</font></div>
<h4>
Services</h4>
Normally, a client program would not instantiate a stub directly.
@@ -817,25 +799,25 @@
returns a stub. This locator is derived from the service clause in
the WSDL. WSDL2Java generates two objects from a service clause.
For example, given the WSDL:
-<p> <service name="AddressBookService">
-<br> <port name="AddressBook"
binding="tns:AddressBookSOAPBinding">
-<br> <soap:address
location="http://localhost:8080/axis/services/AddressBook"/>
-<br> </port>
-<br> </service>
+<div class="example"><br><font face="Courier New,Courier"><service
name="AddressBookService">
+<br> <port name="AddressBook" binding="tns:AddressBookSOAPBinding">
+<br> <soap:address
location="http://localhost:8080/axis/services/AddressBook"/>
+<br> </port>
+<br></service></font></div>
<p>WSDL2Java will generate the service interface:
-<p><font face="Courier New,Courier">public interface AddressBookService
-extends javax.xml.rpc.Service {</font>
-<br><font face="Courier New,Courier"> public String
getAddressBookAddress();</font>
-<br><font face="Courier New,Courier"> public AddressBook
-getAddressBook() throws javax.xml.rpc.ServiceException;</font>
-<br><font face="Courier New,Courier"> public AddressBook
-getAddressBook(URL portAddress) throws javax.xml.rpc.ServiceException;</font>
-<br><font face="Courier New,Courier">}</font>
+<div class="example"><br><font face="Courier New,Courier">public interface
AddressBookService
+extends javax.xml.rpc.Service {
+<br> public String getAddressBookAddress();
+<br> public AddressBook
+getAddressBook() throws javax.xml.rpc.ServiceException;
+<br> public AddressBook
+getAddressBook(URL portAddress) throws javax.xml.rpc.ServiceException;
+<br>}</font></div>
<p>WSDL2Java will also generate the locator which implements this interface:
-<p><font face="Courier New,Courier">public class AddressBookServiceLocator
-extends org.apache.axis.client.Service implements AddressBookService {</font>
-<br><font face="Courier New,Courier"> ...</font>
-<br><font face="Courier New,Courier">}</font>
+<div class="example"><br><font face="Courier New,Courier">public class
AddressBookServiceLocator
+extends org.apache.axis.client.Service implements AddressBookService {
+<br> ...
+<br>}</font></div>
<p>The service interface defines a get method for each port listed in the
service element of the WSDL. The locator is the implementation of this
service interface. It implements these get methods. It serves as
@@ -844,27 +826,25 @@
but you may also specify a different URL when you ask for the PortType.
<p>A typical usage of the stub classes would be as follows:
-<p class="example"><font face="Courier New,Courier">public class Tester
-{</font>
-<br><font face="Courier New,Courier"> public static void main(String
-[] args) throws Exception</font>
-<br><font face="Courier New,Courier"> {</font>
-<br><font face="Courier New,Courier"> // Make a service</font>
-<br><font face="Courier New,Courier"> AddressBookService
-service = new AddressBookServiceLocator();</font>
-<br>
-<p><font face="Courier New,Courier"> // Now use the service
-to get a stub which implements the SDI.</font>
-<br><font face="Courier New,Courier"> AddressBook port
-= service.getAddressBook();</font>
-<p><font face="Courier New,Courier"> // Make the actual
-call</font>
-<div class="example"><font face="Courier New,Courier">
-Address address = new Address(...);</font>
-<br><font face="Courier New,Courier"> port.addEntry("Russell
-Butek", address);</font>
-<br><font face="Courier New,Courier"> }</font>
-<br><font face="Courier New,Courier">}</font></div>
+<div class="example"><br><font face="Courier New,Courier">public class Tester
+{
+<br> public static void main(String
+[] args) throws Exception {
+<br> // Make a service
+<br> AddressBookService
+service = new AddressBookServiceLocator();
+<br>
+<br>
+<br> // Now use the service
+to get a stub which implements the SDI.
+<br> AddressBook port
+= service.getAddressBook();
+<br>
+<br> // Make the actual call
+<br> Address address = new Address(...);
+<br> port.addEntry("Russell Butek", address);
+<br> }
+<br>}</font></div>
<h4>
Server-side bindings</h4>
@@ -872,8 +852,8 @@
a <b>skeleton</b> is a Java framework for the server side. To make
skeleton classes, you just specify the "--skeleton" option to WSDL2Java.
For instance, using the AddressBook.wsdl as we had above:
-<p><font face="Courier New,Courier">% java org.apache.axis.wsdl.WSDL2Java
---skeleton AddressBook.wsdl</font>
+<div class="example"><br><font face="Courier New,Courier">% java
org.apache.axis.wsdl.WSDL2Java
+--skeleton AddressBook.wsdl</font></div>
<p>You will see that WSDL2Java generates all the classes that were generated
before for the client, but it generates a few new files:
<br>
@@ -916,29 +896,25 @@
actual service implementation. Its name is the binding name with
suffix "Skeleton". For example, for the AddressBook binding, WSDL2Java
will generate:
-<p><font face="Courier New,Courier">public class AddressBookSOAPBindingSkeleton
-implements AddressBook,</font>
-<br><font face="Courier New,Courier">
org.apache.axis.wsdl.Skeleton
-{</font>
-<br><font face="Courier New,Courier"> private AddressBook
-impl;</font>
-<p><font face="Courier New,Courier"> public
AddressBookSOAPBindingSkeleton()
-{</font>
-<br><font face="Courier New,Courier">
-this.impl = new AddressBookSOAPBindingImpl();</font>
-<br><font face="Courier New,Courier"> }</font>
-<p><font face="Courier New,Courier"> public
AddressBookSOAPBindingSkeleton(AddressBook
-impl) {</font>
-<br><font face="Courier New,Courier">
-this.impl = impl;</font>
-<br><font face="Courier New,Courier"> }</font>
-<p><font face="Courier New,Courier"> public void
addEntry(java.lang.String
-name, Address address) throws java.rmi.RemoteException</font>
-<br><font face="Courier New,Courier"> {</font>
-<br><font face="Courier New,Courier">
-impl.addEntry(name, address);</font>
-<br><font face="Courier New,Courier"> }</font>
-<br><font face="Courier New,Courier">}</font>
+<div class="example"><br><font face="Courier New,Courier">public class
AddressBookSOAPBindingSkeleton
+implements AddressBook,
+<br> org.apache.axis.wsdl.Skeleton {
+<br> private AddressBook impl;
+<br>
+<br> public AddressBookSOAPBindingSkeleton() {
+<br> this.impl = new
AddressBookSOAPBindingImpl();
+<br> }
+<br>
+<br> public AddressBookSOAPBindingSkeleton(AddressBook impl) {
+<br> this.impl = impl;
+<br> }
+<br>
+<br> public void addEntry(java.lang.String
+name, Address address) throws java.rmi.RemoteException
+<br> {
+<br> impl.addEntry(name, address);
+<br> }
+<br>}</font></div>
<p>(The real skeleton is actually much richer. For brevity I'm just
showing you the basic skeleton.)
<p>The skeleton contains an implementation of the AddressBook service.
@@ -948,12 +924,12 @@
invocation to the real implementation's addEntry method.
<p>Besides the skeleton, WSDL2Java also generates an implementation template
from the binding:
-<p><font face="Courier New,Courier">public class AddressBookSOAPBindingImpl
-implements AddressBook {</font>
-<br><font face="Courier New,Courier"> public void addEntry(String
-name, Address address) throws java.rmi.RemoteException {</font>
-<br><font face="Courier New,Courier"> }</font>
-<br><font face="Courier New,Courier">}</font>
+<div class="example"><br><font face="Courier New,Courier">public class
AddressBookSOAPBindingImpl
+implements AddressBook {
+<br> public void addEntry(String
+name, Address address) throws java.rmi.RemoteException {
+<br> }
+<br>}</font></div>
<p>This template could actually be used as a test implementation but, as
you can see, it doesn't do anything. It is intended that the service
writer fill out the implementation from this template.
@@ -1053,19 +1029,16 @@
Deploy either the skeleton (true) or the implementation (false) in
deploy.wsdd.
In other words, for "true" the service clause in the deploy.wsdd file will
look something like:
-<p><font face="Courier New,Courier"> <service name="AddressBook"
-provider="java:RPC"></font>
-<br><font face="Courier New,Courier"> <parameter
-name="className" value="samples.addr.AddressBookSOAPBindingSkeleton"/></font>
-<br><font face="Courier New,Courier"> ...</font>
-<br><font face="Courier New,Courier"> </service></font>
+<div class="example"><br><font face="Courier New,Courier"><service
name="AddressBook"
+provider="java:RPC">
+<br> <parameter name="className"
value="samples.addr.AddressBookSOAPBindingSkeleton"/>
+<br> ...
+<br></service></font></div>
<p>and for "false" it would look like:
-<p><font face="Courier New,Courier"> <service name="AddressBook"
-provider="java:RPC"></font>
-<br><font face="Courier New,Courier"> <parameter
-name="className" value="samples.addr.AddressBookSOAPBindingImpl"/></font>
-<br><font face="Courier New,Courier"> ...</font>
-<br><font face="Courier New,Courier"> </service></font>
+<div class="example"><br><font face="Courier New,Courier"><service
name="AddressBook" provider="java:RPC">
+<br> <parameter name="className"
value="samples.addr.AddressBookSOAPBindingImpl"/>
+<br> ...
+<br> </service></font></div>
<p>The default for this option is true. This option is only valid
with the --server-side option.
<h4>
@@ -1159,29 +1132,24 @@
<h3>
<a NAME="Java2WSDL: Building WSDL from Java"></a>Java2WSDL: Building WSDL
from Java</h3>
-The Java2WSDL and WSDL2Java emitters make it easy to develop a new web
-service.
-<br>The following sections describe the steps in building a web service
-from a Java interface.
+The Java2WSDL and WSDL2Java emitters make it easy to develop a new web service.
The following sections describe the steps in building a web service from a Java
interface.
<br>
<h4>
Step 1: Provide a Java interface or class</h4>
Write and compile a Java interface (or class) that describes the web service
interface. Here is an example interface that describes a web services
-that can be used to set/query the price of widgets ( <a
href="xml-axis/java/samples/userguide/example6/WidgetPrice.java">../samples/userguide/example6/WidgetPrice.java</a>
-):
-<p><tt><font color="#006600">package samples.userguide.example6;</font></tt>
-<p><tt><font color="#006600">/**</font></tt>
-<br><tt><font color="#006600"> * Interface describing a web service
-to set and get Widget prices.</font></tt>
-<br><tt><font color="#006600"> **/</font></tt>
-<br><tt><font color="#006600">public interface WidgetPrice</font></tt>
-<br><tt><font color="#006600">{</font></tt>
-<br><tt><font color="#006600"> public void setWidgetPrice(String
-widgetName, String price);</font></tt>
-<br><tt><font color="#006600"> public String getWidgetPrice(String
-widgetName);</font></tt>
-<br><tt><font color="#006600">}</font></tt>
+that can be used to set/query the price of widgets (<a
href="../samples/userguide/example6/WidgetPrice.java">samples/userguide/example6/WidgetPrice.java</a>):
+<div class="example"><br><font face="Courier New,Courier">package
samples.userguide.example6;
+<br>/**
+<br> * Interface describing a web service
+to set and get Widget prices.
+<br> **/
+<br>public interface WidgetPrice {
+<br> public void setWidgetPrice(String
+widgetName, String price);
+<br> public String getWidgetPrice(String
+widgetName);
+<br>}</font></div>
<p><b>Note: </b>If you compile your class with debug information, Java2WSDL
will use the debug information to obtain the method parameter names.
<h4>
@@ -1189,9 +1157,7 @@
Use the Java2WSDL tool to create a WSDL file from the interface above.
<p>Here is an example invocation that produces the wsdl file (<tt>wp.wsdl</tt>)
from the interface described in the previous section:
-<p><tt><font color="#009900">java org.apache.axis.wsdl.Java2WSDL -o wp.wsdl
--l"http://localhost:8080/axis/services/WidgetPrice"; -n "urn:Example6"
-p"samples.userguide.example6"
-"urn:Example6" samples.userguide.example6.WidgetPrice</font></tt>
+<div class="example"><br><font face="Courier New,Courier">% java
org.apache.axis.wsdl.Java2WSDL -o wp.wsdl
-l"http://localhost:8080/axis/services/WidgetPrice"; -n
"urn:Example6" -p"samples.userguide.example6" "urn:Example6"
samples.userguide.example6.WidgetPrice</font></div>
<p>Where:
<ul>
<li>
@@ -1371,8 +1337,7 @@
Step 3: Create Bindings using WSDL2Java</h4>
Use the generated wsdl file to build the appropriate client/server bindings
for the web service (see <a href="#WSDL2Java: Building stubs, skeletons, and
data">WSDL2Java</a>):
-<p> <tt><font color="#009900">java org.apache.axis.wsdl.Wsdl2java
--o . -d session -s -Nurn:Example6 samples.userguide.example6 ws.wsdl</font></tt>
+<div class="example"><br><font face="Courier New,Courier">% java
org.apache.axis.wsdl.Wsdl2java -o . -d session -s -Nurn:Example6
samples.userguide.example6 ws.wsdl</font></div>
<p>This will generate the following files:
<ul>
<li>
@@ -1380,7 +1345,7 @@
the default server implementation of the WidgetPrice web service.</li>
<br>You will need to modify the *SoapBindingImpl file to add your implementation
-(see <a
href="xml-axis/java/samples/userguide/example6/WidgetPriceSoapBindingImpl.java">../samples/userguide/example6/WidgetPriceSoapBindingImpl.java</a>
+(see <a
href="../samples/userguide/example6/WidgetPriceSoapBindingImpl.java">../samples/userguide/example6/WidgetPriceSoapBindingImpl.java</a>
).
<li>
<b><tt>WidgetPrice.java</tt></b>: New interface file that contains
@@ -1411,7 +1376,7 @@
code and deploy the web service!
<h2>
<a NAME="published interfaces"></a>Published Axis Interfaces</h2>
-Although you may use any of the interfaces present in Axis, you need to
+Although you may use any of the interfaces and classes present in Axis, you need to
be aware that some are more stable than others since there is a continuing
need to refactor Axis to maintain and improve its modularity.
<p>Hence certain interfaces are designated as <i>published</i>, which means
@@ -1428,9 +1393,98 @@
<p>The current list of published interfaces is as follows:
<ul>
<li>
-No interfaces published so far -- everything is subject to change!</li>
+JAX-RPC interfaces. At the time of this writing, JAX-RPC is still in the public
review stage of its existence, meaning that it may still change. As it does, the
JAX-RPC interfaces may also change. JAX-RPC is expected to become official some time
during the summer of 2002.
+<ul>
+<li>javax.xml.messaging.Endpoint</li>
+<li>javax.xml.messaging.URLEndpoint</li>
+<li>javax.xml.rpc.Call</li>
+<li>javax.xml.rpc.FaultException</li>
+<li>javax.xml.rpc.JAXRPCException</li>
+<li>javax.xml.rpc.ParameterMode</li>
+<li>javax.xml.rpc.Service</li>
+<li>javax.xml.rpc.ServiceException</li>
+<li>javax.xml.rpc.ServiceFactory</li>
+<li>javax.xml.rpc.Stub</li>
+<li>javax.xml.rpc.encoding.DeserializationContext</li>
+<li>javax.xml.rpc.encoding.Deserializer</li>
+<li>javax.xml.rpc.encoding.DeserializerFactory</li>
+<li>javax.xml.rpc.encoding.SerializationContext</li>
+<li>javax.xml.rpc.encoding.Serializer</li>
+<li>javax.xml.rpc.encoding.SerializerFactory</li>
+<li>javax.xml.rpc.encoding.TypeMapping</li>
+<li>javax.xml.rpc.encoding.TypeMappingRegistry</li>
+<li>javax.xml.rpc.handler.Handler</li>
+<li>javax.xml.rpc.handler.HandlerChain</li>
+<li>javax.xml.rpc.handler.HandlerInfo</li>
+<li>javax.xml.rpc.handler.HandlerRegistry</li>
+<li>javax.xml.rpc.handler.MessageContext</li>
+<li>javax.xml.rpc.handler.soap.SOAPMessageContext</li>
+<li>javax.xml.rpc.holders.BigDecimalHolder</li>
+<li>javax.xml.rpc.holders.BigIntegerHolder</li>
+<li>javax.xml.rpc.holders.BooleanHolder</li>
+<li>javax.xml.rpc.holders.BooleanWrapperHolder</li>
+<li>javax.xml.rpc.holders.ByteArrayHolder</li>
+<li>javax.xml.rpc.holders.ByteHolder</li>
+<li>javax.xml.rpc.holders.ByteWrapperArrayHolder</li>
+<li>javax.xml.rpc.holders.ByteWrapperHolder</li>
+<li>javax.xml.rpc.holders.CalendarHolder</li>
+<li>javax.xml.rpc.holders.DateHolder</li>
+<li>javax.xml.rpc.holders.DoubleHolder</li>
+<li>javax.xml.rpc.holders.DoubleWrapperHolder</li>
+<li>javax.xml.rpc.holders.FloatHolder</li>
+<li>javax.xml.rpc.holders.FloatWrapperHolder</li>
+<li>javax.xml.rpc.holders.Holder</li>
+<li>javax.xml.rpc.holders.IntHolder</li>
+<li>javax.xml.rpc.holders.IntegerWrapperHolder</li>
+<li>javax.xml.rpc.holders.LongHolder</li>
+<li>javax.xml.rpc.holders.LongWrapperHolder</li>
+<li>javax.xml.rpc.holders.ObjectHolder</li>
+<li>javax.xml.rpc.holders.QNameHolder</li>
+<li>javax.xml.rpc.holders.ShortHolder</li>
+<li>javax.xml.rpc.holders.ShortWrapperHolder</li>
+<li>javax.xml.rpc.holders.StringHolder</li>
+<li>javax.xml.rpc.namespace.QName</li>
+<li>javax.xml.rpc.server.ServiceLifecycle</li>
+<li>javax.xml.rpc.soap.SOAPFault</li>
+<li>javax.xml.rpc.soap.SOAPHeaderFault</li>
+<li>javax.xml.soap.AttachmentPart</li>
+<li>javax.xml.soap.Detail</li>
+<li>javax.xml.soap.DetailEntry</li>
+<li>javax.xml.soap.FactoryFinder</li>
+<li>javax.xml.soap.MessageFactory</li>
+<li>javax.xml.soap.MimeHeader</li>
+<li>javax.xml.soap.MimeHeaders</li>
+<li>javax.xml.soap.Name</li>
+<li>javax.xml.soap.Node</li>
+<li>javax.xml.soap.SOAPBody</li>
+<li>javax.xml.soap.SOAPBodyElement</li>
+<li>javax.xml.soap.SOAPConnection</li>
+<li>javax.xml.soap.SOAPConnectionFactory</li>
+<li>javax.xml.soap.SOAPConstants</li>
+<li>javax.xml.soap.SOAPElement</li>
+<li>javax.xml.soap.SOAPElementFactory</li>
+<li>javax.xml.soap.SOAPEnvelope</li>
+<li>javax.xml.soap.SOAPException</li>
+<li>javax.xml.soap.SOAPFault</li>
+<li>javax.xml.soap.SOAPFaultElement</li>
+<li>javax.xml.soap.SOAPHeader</li>
+<li>javax.xml.soap.SOAPHeaderElement</li>
+<li>javax.xml.soap.SOAPMessage</li>
+<li>javax.xml.soap.SOAPPart</li>
+<li>javax.xml.soap.Text</li>
+<li>javax.xml.transform.Source</li>
+</ul>
+</li>
+<li>AXIS interfaces:
+<ul>
+<li>org.apache.axis.client.Call</li>
+<li>org.apache.axis.client.Service</li>
+<li>org.apache.axis.client.ServiceFactory</li>
+<li>org.apache.axis.client.Stub</li>
+<li>org.apache.axis.wsdl.WSDL2Java</li>
+<li>org.apache.axis.wsdl.Java2WSDL</li>
+</ul>
</ul>
-
<h2>
<a NAME="tcpmon"></a>Using the Axis TCP Monitor (tcpmon)</h2>
The included "tcpmon" utility can be found in the org.apache.axis.utils
1.14 +1 -0 xml-axis/java/samples/userguide/example5/Client.java
Index: Client.java
===================================================================
RCS file: /home/cvs/xml-axis/java/samples/userguide/example5/Client.java,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Client.java 26 Jan 2002 02:52:38 -0000 1.13
+++ Client.java 9 Mar 2002 20:14:02 -0000 1.14
@@ -91,6 +91,7 @@
call.setTargetEndpointAddress( new java.net.URL(options.getURL()) );
call.setOperationName( new QName("OrderProcessor", "processOrder") );
call.addParameter( "arg1", qn, ParameterMode.PARAM_MODE_IN );
+ call.setReturnType( org.apache.axis.encoding.XMLType.XSD_STRING );
result = (String) call.invoke( new Object[] { order } );
} catch (AxisFault fault) {
