Note that I have not yet update to the lates SOAP build, I might try that in a minute.
For now, here are som capture messages. Responce for boolean, working: <?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/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <SOAP-ENV:Body> <ns1:isLoggedInResponse xmlns:ns1="urn:WebShop" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <return xsi:type="xsd:boolean">true</return> </ns1:isLoggedInResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Respons for Boolean(true), working: <?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/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <SOAP-ENV:Body> <ns1:isLoggedInResponse xmlns:ns1="urn:WebShop" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <return xsi:type="xsd:boolean">true</return> </ns1:isLoggedInResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response for null, causing problems: <?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/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <SOAP-ENV:Body> <ns1:webAllowedResponse xmlns:ns1="urn:WebShop" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <return xsi:type="xsd:boolean" xsi:nil="true"/> </ns1:webAllowedResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The error on the MS client. Note that we have set the WSDL type to anyType. SoapMapper error '80020005' SoapMapper:Converting data for SoapMapper failed inside the typemapper HRESULT=0x80020005: Type mismatch. - SoapMapper:Restoring data into SoapMapper anyType failed HRESULT=0x80020005: Type mismatch. - Client:Unspecified client error. HRESULT=0x80020005: Type mismatch. If we do not change this to anyType but keep the soapenc:boolean, we get: SoapMapper error '80020009' SoapMapper:The schema definition with a targetnamespace of http://schemas.xmlsoap.org/soap/encoding/ for SoapMapper boolean could not be found HRESULT=0x80004005: Unspecified error - SoapMapper:The SoapMapper for element boolean could not be created HRESULT=0x80004005: Unspecified error - WSDLOperation:Initialization of a SoapMapper for operation webAllowed failed HRESULT=0x80004005: Unspecified error - WSDLOperation:Initializing of the output message failed for operation webAllowed > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 30, 2002 4:15 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Wrapped types and MS Toolkit > > > Perhaps someone has already encountered this, but otherwise I > think you will > only get a good answer if you can post (1) the error messages from the MS > client and (2) a capture of the request and response, captured either with > TcpTunnelGui (from Apache SOAP), the SOAP Toolkit Trace Utility, or a > network sniffer. It would be useful to have captures for both the working > (boolean) and failing (Boolean) cases. > > As for Boolean null, I just committed a fix for that a night or two ago. > You will need the newest daily drop or the current CVS code to > get this fix. > > Scott Nichol > > ----- Original Message ----- > From: "Mattias Jiderhamn" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, August 30, 2002 3:04 AM > Subject: Wrapped types and MS Toolkit > > > I'm developing a SOAP service and would like to return wrapped base types, > such as Double and Boolean. > > The person developing a client with the MS SOAP Toolkit clames to have > prolems with theese return values. boolean works fine but Boolean > gives some > type error. First it didn't work at all, but after modifying the WSDL type > to xsd:anyType the values Boolean(true) and Boolean(false) works, but not > null. > > I'm really not an MS programmer, but maybe somebody could give me > some hints > what to do about this problem. > > Thanks in advance, > > Mattias Jiderhamn [EMAIL PROTECTED] > Expert Systems www.expertsystem.se > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
