From john56@example.net Thu Jun 1 16:03:14 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 31559 invoked from network); 1 Jun 2000 16:03:14 -0000 Received: from mercury.sun.com (83.161.120.155) by locus.apache.org with SMTP; 1 Jun 2000 16:03:14 -0000 Received: from ireserver.Ireland.Sun.COM ([83.161.120.155]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA13996 for <john56@example.net>; Thu, 1 Jun 2000 09:03:13 -0700 (PDT) Received: from moe (moe [83.161.120.155]) by ireserver.Ireland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.7) with SMTP id RAA28631 for <john56@example.net>; Thu, 1 Jun 2000 17:03:11 +0100 (BST) Message-Id: <john56@example.net> Date: Thu, 1 Jun 2000 17:02:37 +0100 (BST) From: Sean MacRoibeaird - Sun ireland - Solaris Software - Staff Engineer <john56@example.net> Reply-To: Sean MacRoibeaird - Sun ireland - Solaris Software - Staff Engineer <john56@example.net> Subject: SOAP 1.2 To: john56@example.net MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: BhrJ4/31qUObwqqdcskG4w== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi, As I can't build SOAP 1.2 from the cvs sources, I have tried to use the jar files to run the demos. I get a strange looking "no such method error" in the Xerces space when I run the GetAddress demo: The output is as follows: java demos.addressbook.GetAddress http://moe:8080/ibm-soap/rpcrouter.jsp "John B. Good" >>(Thu Jun 01 16:54:59 GMT+01:00 2000) Processing SOAP request... ----- java.lang.NoSuchMethodError: org.w3c.dom.Node: method getNamespaceURI()Ljava/lang/String; not found ----- What is the Ljava/lang/String bit here. I've looked up the getNamespaceURI() method and it is defined. In the QName.java file there are ^M at the end of the line which should be removed for Unix. Could building the class files with eroneous EOLs cause the screw john56@example.net.<init>(QName.java:23) at com.ibm.cs.xml.QName.matches(QName.java:89) at com.ibm.soap.Envelope.unmarshall(Compiled Code) at _0002frpcrouter_0002ejsprpcrouter_jsp_0._jspService(Compiled Code) at org.apache.jasper.runtime.HttpJspBase.service(Compiled Code) at javax.servlet.http.HttpServlet.service(Compiled Code) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(Compiled Code) at org.apache.jasper.runtime.JspServlet.serviceJspFile(Compiled Code) at org.apache.jasper.runtime.JspServlet.service(Compiled Code) at javax.servlet.http.HttpServlet.service(Compiled Code) at org.apache.tomcat.core.ServletWrapper.handleRequest(Compiled Code) at org.apache.tomcat.core.ContextManager.service(Compiled Code) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed. at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at java.lang.Throwable.<init>(Compiled Code) at java.lang.Exception.<init>(Exception.java:42) at org.xml.sax.SAXException.<init>(SAXException.java:45) at org.xml.sax.SAXParseException.<init>(SAXParseException.java:56) at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:925) at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(Compiled Code) at org.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(Compiled Code) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:817) at com.ibm.cs.xml.XercesParserLiaison.read(XercesParserLiaison.java:28) at com.ibm.soap.rpc.Call.invoke(Call.java:100) at demos.addressbook.GetAddress.main(GetAddress.java:68) Caught SOAPException (SOAP-ENV:Protocol): ---------------------------------------------------------- Sean MacRoibeaird XML Technology Centre Sun Microsystems, East Point Business Park, Dublin 3, Ireland Phone: x19173/771-227-0043 e-mail: john56@example.net From john56@example.net Thu Jun 1 16:39:28 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 52998 invoked by uid 500); 1 Jun 2000 16:39:28 -0000 Delivered-To: john56@example.net Received: (qmail 52995 invoked by uid 1064); 1 Jun 2000 16:39:27 -0000 Date: 1 Jun 2000 16:39:27 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/samples/stockquote DeploymentDescriptor.xml rubys 00/06/01 09:39:26 Modified: java ReleaseNotes.html java/samples/addressbook DeploymentDescriptor.xml java/samples/stockquote DeploymentDescriptor.xml Log: remove more IBM references, update release notes Revision Changes Path 1.2 +104 -121 xml-soap/java/ReleaseNotes.html Index: ReleaseNotes.html =================================================================== RCS file: /home/cvs/xml-soap/java/ReleaseNotes.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ReleaseNotes.html 2000/05/22 00:03:45 1.1 +++ ReleaseNotes.html 2000/06/01 16:39:24 1.2 @@ -4,24 +4,24 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Microsoft FrontPage Express 2.0"> -<title>xml-soap v1.2 Release Notes</title> +<title>XML-SOAP v1.2 Release Notes</title> </head> <body bgcolor="#FFFFFF"> -<h1 align="center">xml-soap v1.2 Release Notes</h1> +<h1 align="center">XML-SOAP v1.2 Release Notes</h1> -<p align="center">May 19, 2000.</p> +<p align="center">May 25, 2000.</p> <h2 align="left">Table of Contents</h2> <ul> - <li><p align="left"><a href="#Features of xml-soap"><font - size="4"><strong>Features of xml-soap</strong></font></a></p> + <li><p align="left"><a href="#Features of XML-SOAP"><font + size="4"><strong>Features of XML-SOAP</strong></font></a></p> </li> <li><p align="left"><a - href="#Using xml-soap for Remote Procedure Calls"><font - size="4"><strong>Using xml-soap for Remote Procedure + href="#Using XML-SOAP for Remote Procedure Calls"><font + size="4"><strong>Using XML-SOAP for Remote Procedure Calls</strong></font></a></p> </li> <li><p align="left"><a href="#RPC over SMTP"><font size="4"><strong>RPC @@ -32,15 +32,8 @@ size="4"><strong>Using Apache Tomcat v3.1 for the Server-side</strong></font></a></p> </li> - <li><p align="left"><a - href="#Using IBM WebSphere v3.02 for the Server-side"><font - size="4"><strong>Using IBM WebSphere v3.02 for the - Server-side</strong></font></a></p> - </li> - <li><p align="left"><a - href="#Running the Server Side Admin Tool to Manage Services"><font - size="4"><strong>Running the Server Side Admin Tool to - Manage Services</strong></font></a></p> + <li><p align="left"><a href="#Managing Services"><font + size="4"><strong>Managing Services</strong></font></a></p> </li> <li><p align="left"><a href="#Tool for Debugging SOAP"><font size="4"><strong>Tool for Debugging SOAP</strong></font></a></p> @@ -50,41 +43,47 @@ </li> <li><p align="left"><a href="#Dependencies"><font size="4"><strong>Dependencies</strong></font></a></p> </li> - <li><p align="left"><a href="#Building from Source"><font - size="4"><strong>Building from Source</strong></font></a></p> - </li> <li><p align="left"><a href="#Bugs"><font size="4"><strong>Bugs</strong></font></a></p> </li> <li><p align="left"><a href="#Authors"><font size="4"><strong>Authors</strong></font></a></p> </li> </ul> -<h2><a name="Features of xml-soap">Features of xml-soap</a></h2> +<h2><a name="Features of XML-SOAP">Features of XML-SOAP</a></h2> <ul> <li>Supports most of the SOAP v1.1 specification</li> <li>Provides server-side infrastructure for deploying, managing and running SOAP enabled services</li> <li>Provides client-side API for invoking SOAP services</li> - <li>Supports two encoding styles: SOAP v1.1 Encoding and XMI - with others to come</li> + <li>Release includes full source under the <em>Apache Software License</em></li> + <li>Supports three encoding styles: SOAP v1.1 Encoding, <img + src="doc/new.gif"> Literal XML and XMI.</li> <li>XMI encoding (available when using Java 1.2.2) supports automatic marshalling and unmarshalling of arbitrary objects</li> <li>SOAP encoding: built-in support is provided for encoding/decoding primitive types, Strings, arbitrary - JavaBeans (using reflection) and 1-dimensional arrays of - these types. For other types user can hand-write - encoder/decoder and register with xml-soap runtime.</li> + JavaBeans (using reflection) and <img src="doc/new.gif"> + 1-dimensional arrays of these types. For other types user + can hand-write encoder/decoder and register with XML-SOAP + runtime.</li> + <li><img src="doc/new.gif"> Literal XML encoding: allows one + to send XML elements (DOM org.w3c.dom.Element objects) as + parameters by embedding the literal XML serialization of + the DOM tree. No code needs to be written to support this + (see the addressbook demo to see a sample use of it).</li> <li>Supports messaging and RPC over two transports: HTTP and SMTP</li> + <li><img src="doc/new.gif"> Supports authoring services in + scripting languages</li> </ul> -<h2><a name="Using xml-soap for Remote Procedure Calls">Using -xml-soap for Remote Procedure Calls</a></h2> +<h2><a name="Using XML-SOAP for Remote Procedure Calls">Using +XML-SOAP for Remote Procedure Calls</a></h2> <p>The org.apache.soap.rpc package supports performing RPC over -SOAP. The xml-soap model is as follows: </p> +SOAP. The XML-SOAP model is as follows: </p> <p>The URI of the method call element is used as the object ID on the remote side. The client side API has a &quot;Call&quot; @@ -92,8 +91,8 @@ name, object ID and parameters. The marshalling/unmarshalling of Java datatypes to/from XML is supported by a type mapping registry (see org.apache.soap.encoding.SOAPMappingRegistry), and -serialization (org.apache.util.xml.Serializer) and deserialization -(org.apache.util.xml.Deserialization) interfaces that marshallers and +serialization (org.apache.soap.util.xml.Serializer) and deserialization +(org.apache.soap.util.xml.Deserialization) interfaces that marshallers and unmarshallers, respectively, must implement. The built-in encoders/decoders are simply implementations of these interfaces that are preregistered in the SOAPMappingRegistry. </p> @@ -125,7 +124,7 @@ <h2><a name="RPC over SMTP">RPC over SMTP</a></h2> -<p>To do RPC over SMTP in xml-soap a certain amount of email +<p>To do RPC over SMTP in XML-SOAP a certain amount of email infrastructure needs to be available. Namely, you need an SMTP server, a POP3 server and an email address that you can use to be the equivalent of the server-side HTTP router. That is, all SOAP @@ -186,7 +185,7 @@ <p>The easiest way to set up for Tomcat is to add a &lt;Context&gt; to conf/server.xml:</p> -<pre>&lt;Context path=&quot;/xml-soap&quot; docBase=&quot;path-to-xml-soap/xml-soap-1.2/webapp&quot; +<pre>&lt;Context path=&quot;/xml-soap&quot; docBase=&quot;path-to-xml-soap/XML-SOAP-1.2/webapp&quot; debug=&quot;1&quot; reloadable=&quot;true&quot; &gt; &lt;/Context&gt;</pre> @@ -211,83 +210,34 @@ </blockquote> <p>Happy SOAP-ing!</p> - -<h2><a name="Using IBM WebSphere v3.02 for the Server-side">Using -IBM WebSphere v3.02 for the Server-Side</a></h2> -<p><strong>Thanks to Paul Fremantle and Paul Tamminga of IBM -Software Group for their assistance with this!</strong></p> +<h2><a name="Managing Services">Managing Services</a></h2> -<p><strong>IMPORTANT</strong>: We use Apache Tomcat 3.1 in our -development. Tomcat comes with an XML parser (lib/xml.jar) which -has the DOM level 1 interfaces. Even if you put Xerces 1.0.3's -xerces.jar in your classpath, the wrong interfaces are found by -any Java code running in Tomcat because the shell script / batch -file that runs Tomcat puts the user's classpath at the end. So, -you must edit tomcat.sh or tomcat.bin in the bin/ directory and -put xerces.jar at the BEGINING of the classpath the script -builds. </p> - -<p>If you run startup.bat, then line 38 of tomcat.bat should look -like this:</p> +<p>XML-SOAP provides an administration tool to manage services. +There are two clients to service manager: an HTML one used via a +browser and a <img src="doc/new.gif"> command-line tool. </p> -<blockquote> - <pre>set CLASSPATH=path-to-xerces\xerces.jar;%CLASSPATH%;%cp%</pre> -</blockquote> +<p>NOTE: If you had previously deployed services to an XML-SOAP +server, then this version will not recognize those services +because the class that was being serialized to represent services +has changed.</p> -<p>If you run startup.sh, add the following after line 111:</p> +<h3>Running the Server Side Admin Tool to Manage Services</h3> -<blockquote> - <pre>CLASSPATH=path-to-xerces/xerces.jar:${CLASSPATH}</pre> -</blockquote> - -<p>The easiest way to set up for Tomcat is to add a -&lt;Context&gt; to conf/server.xml:</p> - -<pre>&lt;Context path=&quot;/xml-soap&quot; docBase=&quot;path-to-xml-soap/xml-soap-1.2/webapp&quot; - debug=&quot;1&quot; reloadable=&quot;true&quot; &gt; -&lt;/Context&gt;</pre> - -<p>Now, make sure you have the jar files from the lib directory -of this distribution on your classpath and startup tomcat. Also -you will want to have on the classpath any of your code that you -want to deploy as services.</p> - -<p>You should be able to deploy services by pointing a browser to</p> - -<blockquote> - <pre><a href="http://hostname:port/xml-soap">http://hostname:port/xml-soap</a></pre> -</blockquote> - -<p>where hostname is the host on which Tomcat is running and port -is the port. See the next section for details on the -aministration tool. The SOAP end-point for invoking services on -this server is:</p> - -<blockquote> - <pre><a href="http://hostname:port/xml-soap">http://hostname:port/xml-soap/rpcrouter.jsp</a></pre> -</blockquote> - -<p>Happy SOAP-ing!</p> - -<h2><a -name="Running the Server Side Admin Tool to Manage Services">Running -the Server Side Admin Tool to Manage Services</a></h2> - -<p>With the xml-soap Administration Tools it is possible to use a +<p>With the XML-SOAP Administration Tools it is possible to use a Web browser to deploy and un-deploy services and to review the list and the definitions of the services deployed on a given SOAP server. </p> <p>Point your browse to <a href="http://hostname:port/xml-soap">http://hostname:port/xml-soap</a> -(see above) and you will get the &quot;xml-soap Admin&quot; +(see above) and you will get the &quot;XML-SOAP Admin&quot; screen with three options:</p> <ul> <li><b>Deploy </b>to deploy a new service. </li> <li><b>Un-deploy </b>to remove a deployed service. </li> - <li><b>List to </b>shows the list of services currently - deployed in the server.</li> + <li><b>List </b>shows the list of services currently deployed + in the server.</li> </ul> <p>The usage of these functions is immediate once one understands @@ -337,42 +287,79 @@ will be forthcoming. </li> </ul> </li> - <li><b>Use static class. </b>If set to<b> </b>&quot;Yes&quot; + <li><b>Method list. </b>Defines the names of the method that + can be invoked on this service object.</li> + <li><b>Provider type.</b><strong> </strong>Indicates whether + the service is implemented using Java or a scripting + language.</li> + <li><b>For Java services, Provider class.</b> Fully specified + class name of the target object servicing the request. </li> + <li><b>For Java services, Use static class. </b>If set to<b> </b>&quot;Yes&quot; the class method that is made available is a static method, and thus no object will be instantiated. When static invocation is used, the &quot;scope&quot; property is not applicable. </li> - <li><b>Method list. </b>Defines the names of the method that - can be invoked on this service object. </li> - <li><b>Provider class.</b> Fully specified class name of the - target object servicing the request. </li> + <li><strong>For script services, Script language.</strong> + Indicates the scripting language used to implement the + service.</li> + <li><strong>For script services, Script filename.</strong> + Name of file containing the script, or</li> + <li><strong>For script services, Script.</strong> The actual + script to run.</li> <li><b>Type mappings. </b>In order to control the serialization and deserialization of specific Java types to and from XML in a particular encoding style, it may be necessary to provide serialization and deserialization classes that know how to perform the correct conversions - for those types. The xml-soap server already includes + for those types. The XML-SOAP server already includes serialization classes for most basic types in the SOAP encoding style, as well as a Bean encoding class that can provide a generic serialization of a bean in terms of its properties. It also includes XMI serializer/deserializer classes to support the XMI encoding style. Since different types may require additional support for - correct serialization, the xml-soap maintains a registry + correct serialization, the XML-SOAP maintains a registry of Serializers and Deserializers. The registry is - accessible to service administrators through the xml-soap + accessible to service administrators through the XML-SOAP administration tool, as well as through a program API. In order to register a (de)serializer class, the class must implement the Serializer or Deserializer interfaces, see - JavaDocs for org.apache.util.xml.Serializer and - org.apache.util.xml.Deserializer .</li> + JavaDocs for org.apache.soap.util.xml.Serializer and + com.org.apache.soap.util.Deserializer .</li> </ul> +<h3>Using the Command Line Tool to Manage Services</h3> + +<p>The command line tool is run by typing java +org.apache.soap.server.ServiceManagerClient. Running this yields:</p> + +<blockquote> + <pre><font color="#0000FF">% java org.apache.soap.server.ServiceManagerClient +Usage: java org.apache.soap.server.ServiceManagerClient url operation arguments +where + url is the XML-SOAP router's URL whose services are managed + operation and arguments are: + deploy deployment-descriptor-file.xml + list + query service-name + undeploy service-name</font></pre> +</blockquote> + +<p>To deploy a service, for example, type:</p> + +<blockquote> + <pre>% java org.apache.soap.server.ServiceManagerClient <a +href="http://hostname:port/xml-soap/rpcrouter.jsp">http://hostname:port/xml-soap/rpcrouter.jsp</a> <strong>deploy</strong> foo.xml</pre> +</blockquote> + +<p>where foo.xml is the deployment descriptor and the URL is +appropriate for your installation.</p> + <h2><a name="Tool for Debugging SOAP">Tool for Debugging SOAP</a></h2> -<p>xml-soap also includes a TCP tunnel / monitor tool that we +<p>XML-SOAP also includes a TCP tunnel / monitor tool that we developed to help debug SOAP and other TCP protocols. The class -org.apache.util.net.TcpTunnelGui can be used to open a port on the +org.apache.soap.util.net.TcpTunnelGui can be used to open a port on the current machine which basically acts as a tunnel to a remote host / port combination. When a connection is made to the port, the tunnel in turn makes a connection to the remote host / port @@ -403,25 +390,16 @@ <ul> <li>XMI encoding requires use of Java 1.2.2 and XML4J 2.0.15. - The rest of xml-soap requires Apache Xerces 1.0.3. Your + The rest of XML-SOAP requires Apache Xerces 1.0.3. Your classpath must have xerces.jar first and then xml4j.jar next <strong>in that order</strong>. </li> - <li>We have been running the server-side code under Apache - Tomcat v3.1. However, we require a DOM level 2 and we - used Apache Xerces 1.0.3. Given that Tomcat ships with - its own XML parser which supports DOM level 1, you have - to do a bit of work to get Tomcat to work right.</li> + <li>Implementing services in scripting languages requires the + use of <a href="http://www.alphaworks.ibm.com/tech/bsf">BSF</a>. + When you download BSF, note carefully the versions of the + various scripting languages supported! [A new release of + BSF is upcoming very shortly.]</li> </ul> -<h2><a name="Building from Source">Building from Source</a></h2> - -<p>You should be able to build everything from the sources in the -src directory. The makefiles use a variable set in -lib/make.include called PATHSEP to indicate whether to use -&quot;;&quot; (for Win32) or &quot;:&quot; (for Unices). Saying -make in the src directory should recurse down and build all -(assuming your classpath is right).</p> - <h2><a name="Bugs">Bugs</a></h2> <p>None that we know of right now ..</p> @@ -441,6 +419,11 @@ IBM TJ Watson Research Center<br> Hawthorne, NY 10532. <br> </p> + Sam Ruby, <a href="mailto:john56@example.net">john56@example.net</a><br> + <br> + Software Solutions<br> + IBM Research Triangle Park<br> + Raleigh, NC 27709<br> </blockquote> </body> </html> 1.3 +1 -1 xml-soap/java/samples/addressbook/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/DeploymentDescriptor.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- DeploymentDescriptor.xml 2000/05/30 10:23:38 1.2 +++ DeploymentDescriptor.xml 2000/06/01 16:39:25 1.3 @@ -1,4 +1,4 @@ -<isd:service xmlns:isd="http://www.ibm.com/namespaces/ibm-soap/deployment" +<isd:service xmlns:isd="http://xml.apache.org/namespaces/xml-soap/deployment" id="urn:AddressFetcher"> <isd:provider type="java" scope="Application" 1.3 +1 -1 xml-soap/java/samples/stockquote/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/stockquote/DeploymentDescriptor.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- DeploymentDescriptor.xml 2000/05/30 10:23:45 1.2 +++ DeploymentDescriptor.xml 2000/06/01 16:39:25 1.3 @@ -1,4 +1,4 @@ -<isd:service xmlns:isd="http://www.ibm.com/namespaces/ibm-soap/deployment" +<isd:service xmlns:isd="http://xml.apache.org/namespaces/xml-soap/deployment" id="urn:i3solutions-delayed-quotes"> <isd:provider type="java" scope="Application" From john56@example.net Thu Jun 1 16:56:47 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 60074 invoked by uid 500); 1 Jun 2000 16:56:47 -0000 Delivered-To: john56@example.net Received: (qmail 60071 invoked by uid 1064); 1 Jun 2000 16:56:47 -0000 Date: 1 Jun 2000 16:56:47 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/src/org/apache/soap Constants.java rubys 00/06/01 09:56:46 Modified: java/samples/addressbook DeploymentDescriptor.xml java/samples/calculator DeploymentDescriptor.xml java/samples/stockquote DeploymentDescriptor.xml java/src/org/apache/soap Constants.java Log: Change namespaces from IBM to apache Revision Changes Path 1.4 +1 -1 xml-soap/java/samples/addressbook/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/DeploymentDescriptor.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DeploymentDescriptor.xml 2000/06/01 16:39:25 1.3 +++ DeploymentDescriptor.xml 2000/06/01 16:56:43 1.4 @@ -1,4 +1,4 @@ -<isd:service xmlns:isd="http://xml.apache.org/namespaces/xml-soap/deployment" +<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:AddressFetcher"> <isd:provider type="java" scope="Application" 1.2 +1 -1 xml-soap/java/samples/calculator/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/calculator/DeploymentDescriptor.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- DeploymentDescriptor.xml 2000/05/22 00:03:51 1.1 +++ DeploymentDescriptor.xml 2000/06/01 16:56:44 1.2 @@ -1,6 +1,6 @@ <?xml version="1.0"?> -<isd:service xmlns:isd="http://www.ibm.com/namespaces/ibm-soap/deployment" +<isd:service xmlns:isd="http://www.ibm.com/ibm-soap/deployment" id="urn:ibm-soap-demo-calculator"> <isd:provider type="script" scope="Application" 1.4 +1 -1 xml-soap/java/samples/stockquote/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/stockquote/DeploymentDescriptor.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DeploymentDescriptor.xml 2000/06/01 16:39:25 1.3 +++ DeploymentDescriptor.xml 2000/06/01 16:56:45 1.4 @@ -1,4 +1,4 @@ -<isd:service xmlns:isd="http://xml.apache.org/namespaces/xml-soap/deployment" +<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:i3solutions-delayed-quotes"> <isd:provider type="java" scope="Application" 1.3 +3 -5 xml-soap/java/src/org/apache/soap/Constants.java Index: Constants.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/Constants.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Constants.java 2000/05/30 10:23:50 1.2 +++ Constants.java 2000/06/01 16:56:46 1.3 @@ -87,13 +87,11 @@ public static String NS_URI_SCHEMA_XSD = "http://www.w3.org/1999/XMLSchema/"; public static String NS_URI_IBM_SOAP = - "http://www.ibm.com/namespaces/ibm-soap"; + "http://xml.apache.org/xml-soap"; public static String NS_URI_IBM_DEPLOYMENT = - "http://www.ibm.com/namespaces/ibm-soap/deployment"; + "http://xml.apache.org/xml-soap/deployment"; public static String NS_URI_LITERAL_XML = - "http://www.ibm.com/namespaces/ibm-soap/literalxml"; - public static String NS_URI_BML_ENC = - "http://www.ibm.com/namespaces/bml"; + "http://xml.apache.org/xml-soap/literalxml"; public static String NS_URI_XMI_ENC = "http://www.ibm.com/namespaces/xmi"; From john56@example.net Thu Jun 1 17:04:00 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 61386 invoked by uid 500); 1 Jun 2000 17:04:00 -0000 Delivered-To: john56@example.net Received: (qmail 61383 invoked by uid 1064); 1 Jun 2000 17:03:59 -0000 Date: 1 Jun 2000 17:03:59 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/src/org/apache/soap/server deploy.gif list.gif soapadmin.gif undeploy.gif rubys 00/06/01 10:03:59 Modified: java/src/org/apache/soap/server deploy.gif list.gif soapadmin.gif undeploy.gif Log: binary this time Revision Changes Path 1.2 +2 -1 xml-soap/java/src/org/apache/soap/server/deploy.gif <<Binary file>> 1.2 +3 -2 xml-soap/java/src/org/apache/soap/server/list.gif <<Binary file>> 1.2 +21 -1 xml-soap/java/src/org/apache/soap/server/soapadmin.gif <<Binary file>> 1.2 +9 -1 xml-soap/java/src/org/apache/soap/server/undeploy.gif <<Binary file>> From john56@example.net Thu Jun 1 19:37:58 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 66006 invoked by uid 500); 1 Jun 2000 19:37:58 -0000 Delivered-To: john56@example.net Received: (qmail 66003 invoked by uid 1064); 1 Jun 2000 19:37:58 -0000 Date: 1 Jun 2000 19:37:58 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/samples/calculator DeploymentDescriptor.xml rubys 00/06/01 12:37:58 Modified: java/samples/calculator DeploymentDescriptor.xml Log: Updated namespace Revision Changes Path 1.3 +1 -1 xml-soap/java/samples/calculator/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/calculator/DeploymentDescriptor.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- DeploymentDescriptor.xml 2000/06/01 16:56:44 1.2 +++ DeploymentDescriptor.xml 2000/06/01 19:37:57 1.3 @@ -1,6 +1,6 @@ <?xml version="1.0"?> -<isd:service xmlns:isd="http://www.ibm.com/ibm-soap/deployment" +<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:ibm-soap-demo-calculator"> <isd:provider type="script" scope="Application" From john56@example.net Fri Jun 2 09:41:39 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 9084 invoked by uid 500); 2 Jun 2000 09:41:39 -0000 Delivered-To: john56@example.net Received: (qmail 9081 invoked by uid 1064); 2 Jun 2000 09:41:39 -0000 Date: 2 Jun 2000 09:41:39 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/samples/addressbook AddressBook.java DeploymentDescriptor.xml README rubys 00/06/02 02:41:39 Modified: java/samples/addressbook AddressBook.java DeploymentDescriptor.xml README Log: update sample to 1.2 Revision Changes Path 1.4 +184 -0 xml-soap/java/samples/addressbook/AddressBook.java Index: AddressBook.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/AddressBook.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- AddressBook.java 2000/05/30 10:23:38 1.3 +++ AddressBook.java 2000/06/02 09:41:31 1.4 @@ -58,6 +58,9 @@ package samples.addressbook; import java.util.*; +import org.w3c.dom.*; +import org.apache.soap.util.*; +import org.apache.soap.util.xml.*; /** * See \samples\addressbook\readme for info. @@ -73,6 +76,9 @@ addEntry("John B. Good", new Address(123, "Main Street", "Anytown", "NY", 12345, new PhoneNumber(123, "456", "7890"))); + addEntry("Bob Q. Public", + new Address(456, "North Whatever", "Notown", "ME", 12424, + new PhoneNumber(987, "444", "5566"))); } public void addEntry(String name, Address address) @@ -90,5 +96,183 @@ } return (Address)name2AddressTable.get(name); + } + + public Element getAllListings() + { + XMLParserLiaison xpl = new XercesParserLiaison(); + Document doc = xpl.createDocument(); + Element bookEl = doc.createElement("AddressBook"); + + bookEl.appendChild(doc.createTextNode("\n")); + + for (Enumeration keys = name2AddressTable.keys(); + keys.hasMoreElements();) + { + String name = (String)keys.nextElement(); + Address address = (Address)name2AddressTable.get(name); + Element listingEl = doc.createElement("Listing"); + Element nameEl = doc.createElement("Name"); + nameEl.appendChild(doc.createTextNode(name)); + listingEl.appendChild(doc.createTextNode("\n ")); + listingEl.appendChild(nameEl); + listingEl.appendChild(doc.createTextNode("\n ")); + Element addressEl = doc.createElement("Address"); + Element streetNumEl = doc.createElement("StreetNum"); + streetNumEl.appendChild(doc.createTextNode(address.getStreetNum() + "")); + addressEl.appendChild(doc.createTextNode("\n ")); + addressEl.appendChild(streetNumEl); + addressEl.appendChild(doc.createTextNode("\n ")); + Element streetNameEl = doc.createElement("StreetName"); + streetNameEl.appendChild(doc.createTextNode(address.getStreetName())); + addressEl.appendChild(streetNameEl); + addressEl.appendChild(doc.createTextNode("\n ")); + Element cityEl = doc.createElement("City"); + cityEl.appendChild(doc.createTextNode(address.getCity())); + addressEl.appendChild(cityEl); + addressEl.appendChild(doc.createTextNode("\n ")); + Element stateEl = doc.createElement("State"); + stateEl.appendChild(doc.createTextNode(address.getState())); + addressEl.appendChild(stateEl); + addressEl.appendChild(doc.createTextNode("\n ")); + Element zipEl = doc.createElement("Zip"); + zipEl.appendChild(doc.createTextNode(address.getZip() + "")); + addressEl.appendChild(zipEl); + addressEl.appendChild(doc.createTextNode("\n ")); + PhoneNumber phone = address.getPhoneNumber(); + Element phoneEl = doc.createElement("PhoneNumber"); + phoneEl.appendChild(doc.createTextNode("\n ")); + Element areaCodeEl = doc.createElement("AreaCode"); + areaCodeEl.appendChild(doc.createTextNode(phone.getAreaCode() + "")); + phoneEl.appendChild(areaCodeEl); + phoneEl.appendChild(doc.createTextNode("\n ")); + Element exchangeEl = doc.createElement("Exchange"); + exchangeEl.appendChild(doc.createTextNode(phone.getExchange())); + phoneEl.appendChild(exchangeEl); + phoneEl.appendChild(doc.createTextNode("\n ")); + Element numberEl = doc.createElement("Number"); + numberEl.appendChild(doc.createTextNode(phone.getNumber())); + phoneEl.appendChild(numberEl); + phoneEl.appendChild(doc.createTextNode("\n ")); + addressEl.appendChild(phoneEl); + addressEl.appendChild(doc.createTextNode("\n ")); + listingEl.appendChild(addressEl); + listingEl.appendChild(doc.createTextNode("\n ")); + bookEl.appendChild(doc.createTextNode(" ")); + bookEl.appendChild(listingEl); + bookEl.appendChild(doc.createTextNode("\n")); + } + + return bookEl; + } + + public int putListings(Element el) + { + Element listingEl = DOMUtils.getFirstChildElement(el); + int count = 0; + + while (listingEl != null) + { + String name = null; + int streetNum = 0; + String streetName = ""; + String city = ""; + String state = ""; + int zip = 0; + int areaCode = 0; + String exchange = ""; + String number = ""; + + Element tempEl = DOMUtils.getFirstChildElement(listingEl); + + while (tempEl != null) + { + String tagName = tempEl.getTagName(); + + if (tagName.equals("Name")) + { + name = DOMUtils.getChildCharacterData(tempEl); + } + else if (tagName.equals("Address")) + { + Element tempEl2 = DOMUtils.getFirstChildElement(tempEl); + + while (tempEl2 != null) + { + String tagName2 = tempEl2.getTagName(); + String content2 = DOMUtils.getChildCharacterData(tempEl2); + + if (tagName2.equals("StreetNum")) + { + streetNum = Integer.parseInt(content2); + } + else if (tagName2.equals("StreetName")) + { + streetName = content2; + } + else if (tagName2.equals("City")) + { + city = content2; + } + else if (tagName2.equals("State")) + { + state = content2; + } + else if (tagName2.equals("Zip")) + { + zip = Integer.parseInt(content2); + } + else if (tagName2.equals("City")) + { + city = content2; + } + else if (tagName2.equals("PhoneNumber")) + { + Element tempEl3 = DOMUtils.getFirstChildElement(tempEl2); + + while (tempEl3 != null) + { + String tagName3 = tempEl3.getTagName(); + String content3 = DOMUtils.getChildCharacterData(tempEl3); + + if (tagName3.equals("AreaCode")) + { + areaCode = Integer.parseInt(content3); + } + else if (tagName3.equals("Exchange")) + { + exchange = content3; + } + else if (tagName3.equals("Number")) + { + number = content3; + } + + tempEl3 = DOMUtils.getNextSiblingElement(tempEl3); + } + } + + tempEl2 = DOMUtils.getNextSiblingElement(tempEl2); + } + } + + tempEl = DOMUtils.getNextSiblingElement(tempEl); + } + + if (name != null) + { + Address address = new Address(streetNum, streetName, city, state, + zip, new PhoneNumber(areaCode, + exchange, + number)); + + addEntry(name, address); + count++; + } + + listingEl = DOMUtils.getNextSiblingElement(listingEl); + } + + return count; } } 1.5 +2 -2 xml-soap/java/samples/addressbook/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/DeploymentDescriptor.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- DeploymentDescriptor.xml 2000/06/01 16:56:43 1.4 +++ DeploymentDescriptor.xml 2000/06/02 09:41:31 1.5 @@ -2,7 +2,7 @@ id="urn:AddressFetcher"> <isd:provider type="java" scope="Application" - methods="getAddressFromName addEntry"> + methods="getAddressFromName addEntry getAllListings putListings"> <isd:java class="samples.addressbook.AddressBook" static="false"/> </isd:provider> <isd:mappings> @@ -17,4 +17,4 @@ java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer" xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/> </isd:mappings> -</isd:service> +</isd:service> \ No newline at end of file 1.3 +5 -3 xml-soap/java/samples/addressbook/README Index: README =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/README,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- README 2000/05/30 10:23:40 1.2 +++ README 2000/06/02 09:41:31 1.3 @@ -12,12 +12,14 @@ Client: ------ -There are 2 sample clients: +There are 4 sample clients: java samples.addressbook.GetAddress + java samples.addressbook.GetAllListings java samples.addressbook.PutAddress + java samples.addressbook.PutListings - Run either one with no args to see the usage. + Run any of them with no args to see the usage. Additional Client Classpath Requirements: @@ -31,7 +33,7 @@ This is a simple service that allows a client to query and populate an address book residing on a server. The address book is pre-populated -with one name: John B. Good +with two names: John B. Good, and Bob Q. Public. Sample Usage: From john56@example.net Fri Jun 2 09:42:32 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 9185 invoked by uid 500); 2 Jun 2000 09:42:32 -0000 Delivered-To: john56@example.net Received: (qmail 9182 invoked by uid 1064); 2 Jun 2000 09:42:32 -0000 Date: 2 Jun 2000 09:42:32 -0000 Message-ID: <john56@example.net> From: john56@example.net To: john56@example.net Subject: cvs commit: xml-soap/java/samples/addressbook GetAllListings.java PutListings.java sample_listings.xml rubys 00/06/02 02:42:32 Added: java/samples/addressbook GetAllListings.java PutListings.java sample_listings.xml Log: update sample to 1.2 Revision Changes Path 1.1 xml-soap/java/samples/addressbook/GetAllListings.java Index: GetAllListings.java =================================================================== /* * The Apache Software License, Version 1.1 * * * Copyright (c) 2000 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "SOAP" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact john56@example.net. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation and was * originally based on software copyright (c) 2000, International * Business Machines, Inc., http://www.apache.org. For more * information on the Apache Software Foundation, please see * <http://www.apache.org/>. */ package samples.addressbook; import java.io.*; import java.util.*; import java.net.*; import org.w3c.dom.*; import org.apache.soap.util.xml.*; import org.apache.soap.*; import org.apache.soap.encoding.*; import org.apache.soap.encoding.soapenc.*; import org.apache.soap.rpc.*; /** * See \samples\addressbook\readme for info. * * @author Matthew J. Duftler (john56@example.net) */ public class GetAllListings { public static void main(String[] args) throws Exception { if (args.length != 1) { System.err.println("Usage:"); System.err.println(" java " + GetAllListings.class.getName() + " SOAP-router-URL"); System.exit (1); } // Process the arguments. URL url = new URL(args[0]); // Build the call. Call call = new Call(); call.setTargetObjectURI("urn:AddressFetcher"); call.setMethodName("getAllListings"); call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML); // Invoke the call. Response resp; try { resp = call.invoke(url, ""); } catch (SOAPException e) { System.err.println("Caught SOAPException (" + e.getFaultCode() + "): " + e.getMessage()); return; } // Check the response. if (!resp.generatedFault()) { Parameter ret = resp.getReturnValue(); Element bookEl = (Element)ret.getValue(); System.out.println(DOM2Writer.nodeToString(bookEl)); } else { Fault fault = resp.getFault(); System.err.println("Generated fault: "); System.out.println (" Fault Code = " + fault.getFaultCode()); System.out.println (" Fault String = " + fault.getFaultString()); } } } 1.1 xml-soap/java/samples/addressbook/PutListings.java Index: PutListings.java =================================================================== /* * The Apache Software License, Version 1.1 * * * Copyright (c) 2000 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "SOAP" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact john56@example.net. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation and was * originally based on software copyright (c) 2000, International * Business Machines, Inc., http://www.apache.org. For more * information on the Apache Software Foundation, please see * <http://www.apache.org/>. */ package samples.addressbook; import java.io.*; import java.util.*; import java.net.*; import org.w3c.dom.*; import org.apache.soap.util.xml.*; import org.apache.soap.*; import org.apache.soap.encoding.*; import org.apache.soap.encoding.soapenc.*; import org.apache.soap.rpc.*; /** * See \samples\addressbook\readme for info. * * @author Matthew J. Duftler (john56@example.net) */ public class PutListings { public static void main(String[] args) throws Exception { if (args.length != 2) { System.err.println("Usage:"); System.err.println(" java " + PutListings.class.getName() + " SOAP-router-URL listings-file.xml"); System.exit (1); } // Process the arguments. URL url = new URL(args[0]); Reader listingsFile = new FileReader(args[1]); XMLParserLiaison xpl = new XercesParserLiaison(); Document doc = xpl.read("- Listings File -", listingsFile); Element root = doc.getDocumentElement(); // Build the call. Call call = new Call(); call.setTargetObjectURI("urn:AddressFetcher"); call.setMethodName("putListings"); call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC); Vector params = new Vector(); params.addElement(new Parameter("newListings", Element.class, root, Constants.NS_URI_LITERAL_XML)); call.setParams(params); // Invoke the call. Response resp; try { resp = call.invoke(url, ""); } catch (SOAPException e) { System.err.println("Caught SOAPException (" + e.getFaultCode() + "): " + e.getMessage()); return; } // Check the response. if (!resp.generatedFault()) { Parameter ret = resp.getReturnValue(); int count = ((Integer)ret.getValue()).intValue(); System.out.println("Added " + count + " listings."); } else { Fault fault = resp.getFault(); System.err.println("Generated fault: "); System.out.println (" Fault Code = " + fault.getFaultCode()); System.out.println (" Fault String = " + fault.getFaultString()); } } } 1.1 xml-soap/java/samples/addressbook/sample_listings.xml Index: sample_listings.xml =================================================================== <AddressBook> <Listing> <Name>Mary Smith</Name> <Address> <StreetNum>888</StreetNum> <StreetName>Broadway</StreetName> <City>Somewhere</City> <State>FL</State> <Zip>87654</Zip> <PhoneNumber> <AreaCode>222</AreaCode> <Exchange>333</Exchange> <Number>4444</Number> </PhoneNumber> </Address> </Listing> <Listing> <Name>Dave Davis</Name> <Address> <StreetNum>919</StreetNum> <StreetName>Baker Lane</StreetName> <City>Sunnytown</City> <State>UT</State> <Zip>43434</Zip> <PhoneNumber> <AreaCode>789</AreaCode> <Exchange>654</Exchange> <Number>3210</Number> </PhoneNumber> </Address> </Listing> </AddressBook> From john56@example.net Fri Jun 2 16:33:54 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 39133 invoked from network); 2 Jun 2000 16:33:54 -0000 Received: from smtp-out001.onemain.com (HELO mail022.mail.onemain.com) (83.161.120.155) by locus.apache.org with SMTP; 2 Jun 2000 16:33:54 -0000 Received: (qmail 29267 invoked from network); 2 Jun 2000 16:33:27 -0000 Received: from unknown (HELO ibs?10.THE?MOON) ([83.161.120.155]) (envelope-sender <john56@example.net>) by mail022.mail.onemain.com (qmail-ldap-1.03) with SMTP for <john56@example.net>; 2 Jun 2000 16:33:27 -0000 Received: by IBS_10 with Internet Mail Service (5.5.2650.21) id <M1JTPHA2>; Fri, 2 Jun 2000 09:29:09 -0700 Message-ID: <712324ACD27BD011B17C0080AD17D38A15298E@IBS_10> From: James Snell <john56@example.net> To: "'john56@example.net'" <john56@example.net> Subject: SOAP C++ Implementation Date: Fri, 2 Jun 2000 09:29:07 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hello All, In addition to the SOAP4J implemenation, I propose that we begin a SOAP4C project that defines a C library for processing an executing a SOAP request. The implementation bits can take the following forms: 1. Apache SOAP Mod 2. IIS ISAPI Extension 3. IIS ASP Component 4. SMTP Listener Component 5. Standalone SOAP Server (supporting HTTP, HTTPS, & SMTP) 6. Client side proxy component a. As a C lib b. As a COM component c. Implements SSL/TLS Let me know what you think. I'm new to the Apache community so I'm not quite sure how things work around here, any pointers would be appreciated. Thanks - James Snell, MCSD www.soap-wrc.com john56@example.net john56@example.net john56@example.net john56@example.net 771-227-0043 From john56@example.net Fri Jun 2 17:16:15 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 62570 invoked from network); 2 Jun 2000 17:16:15 -0000 Received: from e23.nc.us.ibm.com (83.161.120.155) by locus.apache.org with SMTP; 2 Jun 2000 17:16:15 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [83.161.120.155]) by e23.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id MAA02116 for <john56@example.net>; Fri, 2 Jun 2000 12:55:53 -0500 From: john56@example.net Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [83.161.120.155]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.9) with SMTP id NAA31750 for <john56@example.net>; Fri, 2 Jun 2000 13:15:39 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852568F2.005ED04E ; Fri, 2 Jun 2000 13:15:37 -0400 X-Lotus-FromDomain: IBMUS To: john56@example.net Message-ID: <john56@example.net> Date: Fri, 2 Jun 2000 13:05:58 -0400 Subject: Re: SOAP C++ Implementation Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N James Snell wrote: > > In addition to the SOAP4J implemenation, I propose that we begin a SOAP4C > project that defines a C library for processing an executing a SOAP > request. The implementation bits can take the following forms: > > 1. Apache SOAP Mod > 2. IIS ISAPI Extension > 3. IIS ASP Component > 4. SMTP Listener Component > 5. Standalone SOAP Server (supporting HTTP, HTTPS, & SMTP) > 6. Client side proxy component > a. As a C lib > b. As a COM component > c. Implements SSL/TLS Sounds great! The only cautionary note I have is that Don Box is also planning to contribute a C (as well as a Perl) implementation, as well as potentially rewrite large portions of the Java implementation! What state (if any) is your implementation in? If it is just in the concept phase right now, then let's evolve Don's code. If it is essentially ready to go, then would it be possible for Don and a few others to take a peek at the implementation? - Sam Ruby From john56@example.net Fri Jun 2 17:27:16 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 65316 invoked from network); 2 Jun 2000 17:27:16 -0000 Received: from smtp-out001.onemain.com (HELO mail020.mail.onemain.com) (83.161.120.155) by locus.apache.org with SMTP; 2 Jun 2000 17:27:16 -0000 Received: (qmail 7124 invoked from network); 2 Jun 2000 17:26:50 -0000 Received: from unknown (HELO ibs?10.THE?MOON) ([83.161.120.155]) (envelope-sender <john56@example.net>) by mail020.mail.onemain.com (qmail-ldap-1.03) with SMTP for <john56@example.net>; 2 Jun 2000 17:26:50 -0000 Received: by IBS_10 with Internet Mail Service (5.5.2650.21) id <M1JTPHAM>; Fri, 2 Jun 2000 10:22:32 -0700 Message-ID: <712324ACD27BD011B17C0080AD17D38A152993@IBS_10> From: James Snell <john56@example.net> To: "'john56@example.net'" <john56@example.net> Subject: RE: SOAP C++ Implementation Date: Fri, 2 Jun 2000 10:22:31 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I'd have to say half and half. ;-) ... I have bits, but I'm not ready to let them go just yet. - James -----Original Message----- From: john56@example.net [mailto:john56@example.net] Sent: Friday, June 02, 2000 10:06 AM To: john56@example.net Subject: Re: SOAP C++ Implementation James Snell wrote: > > In addition to the SOAP4J implemenation, I propose that we begin a SOAP4C > project that defines a C library for processing an executing a SOAP > request. The implementation bits can take the following forms: > > 1. Apache SOAP Mod > 2. IIS ISAPI Extension > 3. IIS ASP Component > 4. SMTP Listener Component > 5. Standalone SOAP Server (supporting HTTP, HTTPS, & SMTP) > 6. Client side proxy component > a. As a C lib > b. As a COM component > c. Implements SSL/TLS Sounds great! The only cautionary note I have is that Don Box is also planning to contribute a C (as well as a Perl) implementation, as well as potentially rewrite large portions of the Java implementation! What state (if any) is your implementation in? If it is just in the concept phase right now, then let's evolve Don's code. If it is essentially ready to go, then would it be possible for Don and a few others to take a peek at the implementation? - Sam Ruby From john56@example.net Fri Jun 2 23:36:23 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 2950 invoked from network); 2 Jun 2000 23:36:23 -0000 Received: from smtp-out001.onemain.com (HELO mail013.mail.onemain.com) (83.161.120.155) by locus.apache.org with SMTP; 2 Jun 2000 23:36:23 -0000 Received: (qmail 18302 invoked from network); 2 Jun 2000 21:08:41 -0000 Received: from unknown (HELO ibs?10.THE?MOON) ([83.161.120.155]) (envelope-sender <john56@example.net>) by mail013.mail.onemain.com (qmail-ldap-1.03) with SMTP for <john56@example.net>; 2 Jun 2000 21:08:41 -0000 Received: by IBS_10 with Internet Mail Service (5.5.2650.21) id <M1JTPHA5>; Fri, 2 Jun 2000 14:04:20 -0700 Message-ID: <712324ACD27BD011B17C0080AD17D38A15299E@IBS_10> From: James Snell <john56@example.net> To: "'john56@example.net'" <john56@example.net> Subject: SOAP-WRC Date: Fri, 2 Jun 2000 14:04:19 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hello All, I'd like to formally offer my site: www.soap-wrc.com to be used as a general information outlet for news/information relating to the Apache SOAP project. The site has an existing audience, an RSS news feed, etc. I can add a section specifically for Apache related news/links/information, etc. - James Snell From john56@example.net Sat Jun 3 22:18:27 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 75384 invoked from network); 3 Jun 2000 22:18:27 -0000 Received: from e23.nc.us.ibm.com (83.161.120.155) by locus.apache.org with SMTP; 3 Jun 2000 22:18:27 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [83.161.120.155]) by e23.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id RAA18690; Sat, 3 Jun 2000 17:58:36 -0500 From: john56@example.net Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [83.161.120.155]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.9) with SMTP id SAA28150; Sat, 3 Jun 2000 18:18:25 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852568F3.007A873E ; Sat, 3 Jun 2000 18:18:20 -0400 X-Lotus-FromDomain: IBMUS To: john56@example.net cc: john56@example.net, john56@example.net Message-ID: <john56@example.net> Date: Sat, 3 Jun 2000 09:36:22 -0400 Subject: Re: SOAP 1.2 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > As I can't build SOAP 1.2 from the cvs sources, I assume you were trying IBM-SOAP4J? Have you tried Apache XML-SOAP yet? If not, follow the instructions at the bottom of http://xml.apache.org/cvs.html . You will also need to get jakarta-ant, which is a *much* better build tool than gnu make, IMHO. > I have tried to use the jar files to run the demos. I get a > strange looking "no such method error" in the Xerces space > when I run the GetAddress demo: > > The output is as follows: > > java.lang.NoSuchMethodError: org.w3c.dom.Node: method > getNamespaceURI()Ljava/lang/String; not found Generally speaking, this usually means that you have multiple XML parsers in your class path, and don't have them in the correct order. One of the messiest problems that remain with deploying Java web servers today, IMHO - everybody is converting to XML (a good thing) but coding in specific dependencies on their favorite XML parser (a bad thing, if you use components from multiple sources). The next release of Tomcat will remove its dependency on the Sun Java parser (a.k.a., project X) in favor of JAXP. I am also told that Rajiv Mordani has the changes necessary to get the Apache soap implementation to use JAXP too. Anyway, for best results at the moment, put the Xerces XML 1.0.3 or later parser *first* in your CLASSPATH. - Sam Ruby From john56@example.net Mon Jun 5 15:43:27 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 96481 invoked from network); 5 Jun 2000 15:43:27 -0000 Received: from e21.nc.us.ibm.com (83.161.120.155) by locus.apache.org with SMTP; 5 Jun 2000 15:43:27 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [83.161.120.155]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA121134 for <john56@example.net>; Mon, 5 Jun 2000 11:33:47 -0500 From: john56@example.net Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [83.161.120.155]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.9) with SMTP id LAA22852 for <john56@example.net>; Mon, 5 Jun 2000 11:43:22 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852568F5.00565E16 ; Mon, 5 Jun 2000 11:43:21 -0400 X-Lotus-FromDomain: IBMUS To: john56@example.net Message-ID: <john56@example.net> Date: Mon, 5 Jun 2000 10:29:06 -0400 Subject: Re: SOAP-WRC Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N James Snell wrote: > I'd like to formally offer my site: www.soap-wrc.com to be used as a > general information outlet for news/information relating to the Apache > SOAP project. The site has an existing audience, an RSS news feed, > etc. I can add a section specifically for Apache related > news/links/information, etc. I'd like to keep the xml projects all on the same site. Cross links would be a good idea, and we could always use help in keeping the Apache site up to date.... - Sam Ruby From john56@example.net Mon Jun 5 18:04:49 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 29047 invoked from network); 5 Jun 2000 18:04:49 -0000 Received: from smtp-out001.onemain.com (HELO mail015.mail.onemain.com) (83.161.120.155) by locus.apache.org with SMTP; 5 Jun 2000 18:04:49 -0000 Received: (qmail 7122 invoked from network); 5 Jun 2000 18:04:17 -0000 Received: from unknown (HELO ibs?10.THE?MOON) ([83.161.120.155]) (envelope-sender <john56@example.net>) by us015.mail.onemain.com (qmail-ldap-1.03) with SMTP for <john56@example.net>; 5 Jun 2000 18:04:17 -0000 Received: by IBS_10 with Internet Mail Service (5.5.2650.21) id <MGLQ7XQH>; Mon, 5 Jun 2000 10:59:52 -0700 Message-ID: <712324ACD27BD011B17C0080AD17D38A1B5C1A@IBS_10> From: James Snell <john56@example.net> To: "'john56@example.net'" <john56@example.net> Subject: RE: SOAP-WRC Date: Mon, 5 Jun 2000 10:59:41 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Understandable :-) I've already updated my links from the Alphaworks site to the Apache site. - James -----Original Message----- From: john56@example.net [mailto:john56@example.net] Sent: Monday, June 05, 2000 7:29 AM To: john56@example.net Subject: Re: SOAP-WRC James Snell wrote: > I'd like to formally offer my site: www.soap-wrc.com to be used as a > general information outlet for news/information relating to the Apache > SOAP project. The site has an existing audience, an RSS news feed, > etc. I can add a section specifically for Apache related > news/links/information, etc. I'd like to keep the xml projects all on the same site. Cross links would be a good idea, and we could always use help in keeping the Apache site up to date.... - Sam Ruby From john56@example.net Mon Jun 5 19:23:39 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 74355 invoked from network); 5 Jun 2000 19:23:39 -0000 Received: from igw8.watson.ibm.com (83.161.120.155) by locus.apache.org with SMTP; 5 Jun 2000 19:23:39 -0000 Received: from mailhub.watson.ibm.com (mailhub.watson.ibm.com [83.161.120.155]) by igw8.watson.ibm.com (8.9.3/8.9.3/05-14-1999) with ESMTP id PAA16868; Mon, 5 Jun 2000 15:23:38 -0400 Received: from lanka.watson.ibm.com (lanka.watson.ibm.com [83.161.120.155]) by mailhub.watson.ibm.com (8.8.7/Feb-20-98) with ESMTP id PAA08226; Mon, 5 Jun 2000 15:23:37 -0400 Received: from lankabook (lig32-227-111-150.us.lig-dial.ibm.com [83.161.120.155]) by lanka.watson.ibm.com (8.8.7/8.8.8) with SMTP id PAA22709; Mon, 5 Jun 2000 15:23:35 -0400 (EDT) Message-ID: <john56@example.net> From: "Sanjiva Weerawarana" <john56@example.net> To: <john56@example.net> Cc: <john56@example.net>, <john56@example.net> Subject: Re: SOAP 1.2 Date: Mon, 5 Jun 2000 15:23:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >> I have tried to use the jar files to run the demos. I get a >> strange looking "no such method error" in the Xerces space >> when I run the GetAddress demo: >> >> The output is as follows: >> >> java.lang.NoSuchMethodError: org.w3c.dom.Node: method >> getNamespaceURI()Ljava/lang/String; not found The problem here is that your classpath has a DOM Level 1 parser and not a Level 2 parser. The SOAP code requires a namespace-aware parser and uses Xerces 1.0.3. I have heard that the SOAP code does not work with Xerces 1.1.0, but haven't had a chance to find and fix the problem yet. Sanjiva. From john56@example.net Tue Jun 6 07:44:36 2000 Return-Path: <john56@example.net> Mailing-List: contact john56@example.net; run by ezmlm Delivered-To: mailing list john56@example.net Received: (qmail 26381 invoked from network); 6 Jun 2000 07:44:36 -0000 Received: from lumberjack.collab.net (HELO ambient.collab.net) (83.161.120.155) by locus.apache.org with SMTP; 6 Jun 2000 07:44:36 -0000 Received: from localhost (ed@localhost) by ambient.collab.net (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id BAA26821 for <john56@example.net>; Tue, 6 Jun 2000 01:18:44 -0700 X-Authentication-Warning: ambient.collab.net: ed owned process doing -bs Date: Tue, 6 Jun 2000 01:18:44 -0700 (PDT) From: Ed Korthof <john56@example.net> X-Sender: john56@example.net To: john56@example.net Subject: "No Deserializer found ..." problems/looking for source code Message-ID: <john56@example.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi -- I'd post this to the users list, but it seems inactive. I'm trying to test out SOAP for a project I'm considering using it on. So I've set up Tomcat 3.1, downloaded the most recent xerces and (i think) all the other requirements for the addressbook demo. I'm able to use the soap manager servlet, to list deployed services, to deploy the addressbook service, and to undeploy it. However, when I try to operate through the command line, I get nothing but trouble. I've tried TCP Tunnel/Monitor, and it helped me reach this point -- but it's not giving me much more useful information, nor are the logs. I tried this with IBM's distribution, and then with the distribution from xml.apache.org. I've yet to get either of them to work, though I got a bit farther with IBM's. I can't use the web based deploy .jsp w/ the distribution from xml.apache.org -- I get the following error in my tomcat.log: ***** ed@ambient:~/jakarta/build/tomcat > tail -20 logs/tomcat.log org.apache.jasper.JasperException: Unable to compile .../_0002fdeploy_0002ejspdeploy_jsp_0.java:148: No variable NS_URI_BML_ENC defined in class org.apache.soap.Constants. org.apache.soap.Constants.NS_URI_BML_ENC}; ^ 1 john56@example.net(Compiler.java:247) at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java:413) [snip] ***** I used javap on the soap.jar which comes with this distribution; it has an org.apache.soap.Constants class which is, in fact, missing that constant: ***** ed@ambient:~/jakarta/xml-soap/webapps > javap -classpath /home/ed/lib/soap.jar org.apache.soap.Constants | grep BML ed@ambient:~/jakarta/xml-soap/webapps > javap -classpath /home/ed/lib/IBM-SOAP.jar com.ibm.soap.Constants | grep BML public static java.lang.String NS_URI_BML_ENC; ed@ambient:~/jakarta/xml-soap/webapps > ***** Anyway, on account of that error (and the fact that I can't find a distribution on xml.apache.org which includes source, so I can't fix it myself), much of this message concerns the IBM version. It's almost the same -- and I'm seeing the same sort of errors, so hopefully the same solution will apply. Of course, if someone can direct me to a distribution which includes source code, that'd also make me happy. ;-) I have shell access to apache.org, so it is possible (though a PITA) for me to get the source ... but I'd rather have a snapshot from some point when the code was stable, and it'd be good if those w/o shell access on apache.org could get the source too. First, here's my classpath: /home/ed/lib/xerces.jar:/home/ed/lib/parser.jar: /home/ed/lib/jaxp.jar:/home/ed/lib/ant.jar: /home/ed/lib/servlet.jar:/home/ed/lib/servlet.jar: /home/ed/lib/xerces.jar:/home/ed/lib/IBM-SOAP.jar: /home/ed/lib/pop3.jar:/home/ed/lib/smtp.jar: /home/ed/lib/xmisoap.jar:/home/ed/jakarta/IBM-SOAP-1.2 The errors which I'm getting all relate to serialization. This application uses just the default SOAP serializer, but clearly something is going wrong ... Anyway, more detailed debugging information follows. When I try to deploy the addressbook demo from the command line, here's the error I see: ***** ed@ambient:~/jakarta/xml-soap/lib > java \ com.ibm.soap.server.ServiceManagerClient \ http://localhost:8081/ibm-soap/rpcrouter.jsp \ deploy \ ~/jakarta/IBM-SOAP-1.2/demos/addressbook/DeploymentDescriptor.xml Ouch, the call failed: Fault Code = SOAP-ENV:Client Fault String = No Deserializer found to deserialize a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding style 'null'. ed@ambient:~/jakarta/xml-soap/lib > ***** TCP Tunnel/Monitor shows the following: ***** SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema/instance/" xmlns:xsd="http://www.w3.org/1999/XMLSchema/"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Client</faultcode> <faultstring>No Deserializer found to deserialize a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding style 'null'.</faultstring> <faultactor>/ibm-soap/rpcrouter.jsp</faultactor> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ***** And the error logs don't give me any useful information. I get the same results whether or not this has been deployed using the web interface. Since I can deploy this through the web interface, I also tried using the addressbook demo as per its instructions. I tried with the encoding style omitted, and with it specified as '-SOAP': ***** ed@ambient:~/jakarta/xml-soap/lib > java demos.addressbook.GetAddress http://localhost:8081/ibm-soap/rpcrouter.jsp "John B. Good" Generated fault: Fault Code = SOAP-ENV:Client Fault String = No Deserializer found to deserialize a 'http://schemas.xmlsoap.org/soap/envelope/:Parameter' using encoding style 'null'. ed@ambient:~/jakarta/xml-soap/lib > java demos.addressbook.GetAddress -SOAP http://localhost:8081/ibm-soap/rpcrouter.jsp "John B. Good" Caught SOAPException (SOAP-ENV:Client): No Serializer found to serialize a 'com.ibm.soap.rpc.Parameter' using encoding style 'SOAP'. ed@ambient:~/jakarta/xml-soap/lib > ***** In
{'source': 'Apache Software Foundation Public Mail Archives'}