You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/03/23 16:31:31 UTC
[Bug 1095] New - Ver 1.3.1 won't operate with SOAP (1.2.3 works fine)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1095
*** shadow/1095 Fri Mar 23 07:31:31 2001
--- shadow/1095.tmp.1230 Fri Mar 23 07:31:31 2001
***************
*** 0 ****
--- 1,82 ----
+ +============================================================================+
+ | Ver 1.3.1 won't operate with SOAP (1.2.3 works fine) |
+ +----------------------------------------------------------------------------+
+ | Bug #: 1095 Product: Xerces-J |
+ | Status: NEW Version: 1.3.0 |
+ | Resolution: Platform: All |
+ | Severity: Major OS/Version: All |
+ | Priority: High Component: Core |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-j-dev@xml.apache.org |
+ | Reported By: paduffy@cisco.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ Dozens of people are/have struggled with this problem in the last few weeks...
+
+ Xerces J 1.3.1 has the following problems when run with SOAP 2.1 (Xerces 1.2.3
+ does not exhibit these problems). Xerces/SOAP client reports the following
+
+ SOAPException=SOAP-ENV:Client, A
+ ''http://schemas.xmlsoap.org/soap/envelope/:Fault" element must contain a
+ : "faultcode" element.
+
+ The SOAP Request:
+
+ POST /soap/servlet/rpcrouter HTTP/1.0
+ Host: localhost:8070
+ Content-Type: text/xml; charset=utf-8
+ Content-Length: 501
+ SOAPAction: ""
+
+ <?xml version='1.0' encoding='UTF-8'?>
+ <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>
+ <ns1:getRate xmlns:ns1="urn:demo1:exchange"
+ SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
+ <country1 xsi:type="xsd:string">USA</country1>
+ <country2 xsi:type="xsd:string">japan</country2>
+ </ns1:getRate>
+ </SOAP-ENV:Body>
+ </SOAP-ENV:Envelope>
+
+ The SOAP Repsonse:
+
+ HTTP/1.0 400 Bad Request
+ Content-Type: text/xml; charset=utf-8
+ Content-Length: 472
+ Set-Cookie2: JSESSIONID=2np2a3c101;Version=1;Discard;Path="/soap"
+ Set-Cookie: JSESSIONID=2np2a3c101;Path=/soap Servlet-Engine: Tomcat Web
+ Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.3.0_02; Windows NT 4.0 x86;
+ java.vendor=Sun Microsystems Inc.)
+
+ <?xml version='1.0' encoding='UTF-8'?>
+ <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>Unable to resolve namespace URI for 'xsd'.</faultstring>
+ <faultactor>/soap/servlet/rpcrouter</faultactor>
+ </SOAP-ENV:Fault>
+ </SOAP-ENV:Body>
+ </SOAP-ENV:Envelope>
+
+ Two questions...
+
+ 1. Why can't xerces resolve the xsd namespace URI.
+ 2. Why can't xerces parse the response's faultcode.
+
+ Running
+
+ J2SDK 1.3.0.02
+ Tomcat 3.2.1
+ Soap 2.1
+ Xerces 1.3.1
+ Jaf 1.0.1
+ Javamail 1.2
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org