ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> Apache-Soap-Users
Apache-Soap-Users
RE: vs. problems
by Frank Starsinic other posts by this author
Jan 4 2001 4:38PM messages near this date
Re: vs. problems | Re: vs. problems
i belive i tried it both ways. on more than one occasion, the only thing
that was different was the <soap>  and <soap-env> stuff. everything else
i left the same. still didn't work.  i will re-test that but i'm sure
that was the only difference.


what did you think about getting <soap>  (instead of <soap-env>) tags
returned? does this give
us a hint at all?

frank

>  -----Original Message-----
>  From: Simon Fell [mailto:soap@[...].uk]
>  Sent: Thursday, January 04, 2001 2:29 PM
>  To: soap-user@[...].org
>  Subject: Re: <soap> vs. <soap-env> problems
> 
> 
>  ok, i think we're getting somewhere, this request is different from
>  the one that works in more than just the SOAP / SOAP-ENV prefix. The
>  one that works specifies the standard SOAP encoding,
>  SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> 
>  whilst the one that's failing is using an apache specific encoding
>  SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"
> 
>  The server is failing because it doesn't know how to handle this
>  encoding style. you need to change your request to specify the
>  standard encoding style.
> 
>  Microsoft now have 2 SOAP toolkits, the first one they released has a
>  core object called ROPE (Remote object proxy engine), whilst the new
>  toolkit is called the SOAP SDK. I usually call the first toolkit the
>  ROPE toolkit so that it's hopefully clear which one is being
>  referenced (of course there's also all the SOAP stuff in the .NET beta
>  as well)
> 
>  Cheers
>  Simon
>  www.pocketsoap.com
> 
>  On Thu, 4 Jan 2001 10:56:16 -0500, in soap you wrote:
> 
>  >Here's the transaction on a failure. the company on the
>  other end swears
>  >that they
>  >have the latest version of the ms toolkit. if that were the
>  case, would
>  >their
>  >transmission send back <soap> tags?????  seems like it would
>  send back
>  ><soap-env>
>  >tags if they were using the lastest soap toolkit?
>  >
>  >rope toolkit? is that different than the soap toolkit?
>  >
>  >frank
>  >
>  >Here's the request...
>  >##################################################################
>  >POST /Mentis/Mentis.asp HTTP/1.0
>  >Host: twc
>  >Content-Type: text/xml
>  >Content-Length: 841
>  >SOAPAction: "http://twc/Mentis/Mentis.asp#Serviceability"
>  >
>  ><SOAP-ENV:Envelope
>  >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xm
>  >lns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>  >xmlns:xsd="http://www.w3.org
>  >/1999/XMLSchema">
>  ><SOAP-ENV:Body>
>  ><ns1:Serviceability xmlns:ns1="Mentis"
>  >SOAP-ENV:encodingStyle="http://xml.apache
>  >.org/xml-soap/literalxml">
>  ><QuerySubscriberRequest>
>  ><Serviceability>
>  >                        <EXTERN_SYS_XREF>255</EXTERN_SYS_XREF>
>  >                        <WFE_TRAN_TYPE>SERVICEABILITY</WFE_TRAN_TYPE>
>  >                        <ADDRESS1>4308 ALLEN DR</ADDRESS1>
>  >                        <ADDRESS2/>
>  >                        <CITY>COLUMBUS</CITY>
>  >                        <STATE>OH</STATE>
>  >                        <ZIP>43213</ZIP>
>  >                        <ZIP4/>
>  >                        <HOME_PHONE>6143956456</HOME_PHONE>
>  >                        <ACCOUNT_NO/>
>  >                        <HOUSE_KEY/>
>  >                        <STATUS_CODE>0</STATUS_CODE>
>  >                        <ERROR_CODE>0</ERROR_CODE>
>  >                        <DESCR/>
>  >                </Serviceability>
>  ></QuerySubscriberRequest>
>  ></ns1:Serviceability>
>  ></SOAP-ENV:Body>
>  ></SOAP-ENV:Envelope>
>  >
>  >
>  >Here's the response...
>  >##################################################################
>  >HTTP/1.1 200 OK
>  >Server: Microsoft-IIS/4.0
>  >Date: Tue, 02 Jan 2001 23:04:06 GMT
>  >MessageType: CallResponse
>  >Content-Type: text/xml
>  >Expires: Tue, 02 Jan 2001 23:04:06 GMT
>  >Set-Cookie: ASPSESSIONIDQQGQGRGK=DNNDGPABLDNIHENBPLJMPAPI; path=/
>  >Cache-control: private
>  >
>  ><?xml version="1.0"?>
>  ><SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
>  >SOAP:encod
>  >ingStyle="http://schemas.xmlsoap.org/soap/encoding/">
>  ><SOAP:Body>
>  >
>  ><SOAP:Fault>
>  ><faultcode>300</faultcode><faultstring>Nothing was
>  >posted</faultstring><faultact
>  >or>300</faultactor><detail>Nothing was posted</detail></SOAP:Fault>
>  ></SOAP:Body>
>  ></SOAP:Envelope>
>  >
>  >
>  >> -----Original Message-----
>  >> From: Simon Fell [mailto:soap@[...].uk]
>  >> Sent: Thursday, January 04, 2001 1:25 PM
>  >> To: soap-user@[...].org
>  >> Subject: Re: <soap> vs. <soap-env> problems
>  >>
>  >>
>  >> but when the request uses SOAP-ENV, it fails, right ?. what's the
>  >> reply look like in this case ?,
>  >>
>  >
>  >
>  >---------------------------------------------------------------------
>  >To unsubscribe, e-mail: soap-user-unsubscribe@[...].org
>  >For additional commands, email: soap-user-help@[...].org
> 
> 
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: soap-user-unsubscribe@[...].org
>  For additional commands, email: soap-user-help@[...].org
> 
Thread:
Alex Cruise
Christian Weyer
Frank Starsinic
Frank Starsinic
Frank Starsinic
Simon Fell
Frank Starsinic
Simon Fell
Frank Starsinic
Simon Fell
Frank Starsinic
Simon Fell
Frank Starsinic
Frank Starsinic
Glen Daniels
Frank Starsinic
Simon Fell

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved