You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by du...@apache.org on 2001/05/23 20:52:36 UTC
cvs commit: xml-soap/java/docs/guide deploy.html rpcclient.html
duftler 01/05/23 11:52:34
Modified: java/docs/guide deploy.html rpcclient.html
Log:
More doc updates from BIll
Submitted by: Bill Nagy (nagy@watson.ibm.com)
Reviewed by: Matthew J. Duftler (duftler@us.ibm.com)
Revision Changes Path
1.7 +9 -4 xml-soap/java/docs/guide/deploy.html
Index: deploy.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/deploy.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- deploy.html 2001/05/22 15:05:08 1.6
+++ deploy.html 2001/05/23 18:52:25 1.7
@@ -30,7 +30,7 @@
class (including a normal Java Bean) looks
like the following:</P>
<PRE><isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
- id="urn:<I><STRONG>service-urn</STRONG></I>" [type="message"]><BR> <isd:provider type="java"<BR> scope="Request | Session | Application"<BR> methods="<I><STRONG>exposed-methods</STRONG></I>"><BR> <isd:java class="<I><STRONG>implementing-class</STRONG></I>" [static="true|false"]/><BR> </isd:provider><BR> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
+ id="urn:<I><STRONG>service-urn</STRONG></I>" [type="message"] [checkMustUnderstands="true|false"]><BR> <isd:provider type="java"<BR> scope="Request | Session | Application"<BR> methods="<I><STRONG>exposed-methods</STRONG></I>"><BR> <isd:java class="<I><STRONG>implementing-class</STRONG></I>" [static="true|false"]/><BR> </isd:provider><BR> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service></PRE>
<P>Where <I><STRONG>service-urn</STRONG></I> is the URN that you want to give to a service,
<I><STRONG>exposed-methods</STRONG></I> is a space separated list of methods which
@@ -39,9 +39,14 @@
exposed. On the <service> element,
there is an optional attribute called <I>type</I> which may be set to the value "message"
if the service is document-oriented instead
-of being an RPC invoked service. On the <java>
-element, there is an optional attribute called
-<I>static</I>, which may be set to either "true"
+of being an RPC invoked service, and an optional
+attribute called <I>checkMustUnderstands</I> which may be set to either "true"
+or "false" depending upon whether
+or not you want the server to throw a Fault
+if there were SOAP headers in the request
+which were marked as MustUnderstand. On the
+<java> element, there is an optional
+attribute called <I>static</I>, which may be set to either "true"
or "false", depending upon whether
or not the methods which are being exposed
are static or not. The <provider> element
1.7 +20 -8 xml-soap/java/docs/guide/rpcclient.html
Index: rpcclient.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/rpcclient.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rpcclient.html 2001/05/23 15:38:23 1.6
+++ rpcclient.html 2001/05/23 18:52:26 1.7
@@ -26,7 +26,8 @@
<OL>
<LI><B>Obtain the interface description of the SOAP
service, so that you know what the signatures
- of the methods that you wish to invoke are.</B><BR>
+ of the methods that you wish to invoke
+ are.</B><BR>
You can either look at a WSDL file (or
at
some other interface definition format)
@@ -34,6 +35,20 @@
the service, or directly at its implementation.<BR>
<BR>
+ <LI><B>Make sure that there are serializers registered
+ for all parameters which you will be sending,
+ and deserializers for all information which
+ you will be receiving back.</B><BR>
+ Parameters must be serialized into/deserialized
+ from XML before they can be transmitted/received,
+ and so Apache SOAP provides a number of pre-defined
+ serializers/deserializers which are available.
+ If you need to transmit or receive a type
+ which has not been registered, then you will
+ need to <A href="serializer.html">write and register your own serializer/deserializer</A>.<BR><BR>
+
+
+
<LI><B>Create the org.apache.soap.rpc.RPCMessage.Call
object.</B><BR>
The Apache SOAP Call object is the main interface
@@ -61,13 +76,10 @@
using the setParams(...) method.</B><BR>
Make sure that you have the same number of
parameters with the same types as the service
- is expecting. Parameters must be serialized
- into XML before they can be transmitted,
- and so Apache SOAP provides a number of pre-defined
- serializers/deserializers which are available.
- If you need to transmit a type which has
- not been registered, then you will need to
- <A href="serializer.html">write and register your own serializer/deserializer</A>.<BR>
+ is expecting. Also make sure that there are
+ registered serializers/deserializers for
+ the objects which you will be transmitting/receiving.
+ (See step 2.)<BR>
<BR>
<LI><B>Execute the Call object's invoke(...) method