Definitely sounds like something to try. Thanks! ___________________ Sent from my Gen 1, Day 1 iPad 8)
On Mar 16, 2011, at 4:56 PM, "Robert Shubert" <[email protected]> wrote: > Dale, > > > > Looking over the docs for web services, it looks like there are a few issues > here. I’m not sure where the “No SOAP Request” error is coming from, but it > seems that some header information isn’t being created or handled properly. > > > > As for he Content-Type issue. Again, this does seem to match the > documentation, but you should be able to change the header by assigning a new > header to request$httpHeader within the TCF method. It’s a little tricky to > formulate a full and correct header, but it’s possible. > > > > I can’t say for sure if that will fix the problems. > > > > Robert > > > > From: Dale Graham [mailto:[email protected]] > Sent: Wednesday, March 16, 2011 11:55 AM > To: [email protected] > Subject: Witango-Talk: Issue with type-content for webservices > > > > I was reviewing Witango 6 and webservices, and started to begin from scratch > and follow the directions... After a few glitches (resolved), web services > are apparently correctly configured but ... > > > > When I go to http://localhost/webservices/WhatsTheTime.taf (a taf that > accesses the webservice and shows the results) > > > > I get a response indicating that the webservice is operational (my > webservices directory is located at the root of /Documents, which is webroot) > and that there was a correct response to the soap request. > > > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope";> > > <env:Body> > <mns:WhatsTheTime_Response xmlns:mns="witangowebservices"> > <CurrentTime>03/16/2011 11:10:28</CurrentTime> > <status>OK</status> > </mns:WhatsTheTime_Response> > </env:Body> > > </env:Envelope> > > > but when I go to http://WhatsTheTime.wws > > > > > > I get this, apparently indicating that a soap request either wasn't correct > or was empty: > > > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope";> > > <env:Body> > <env:Fault> > <mns:faultstring xmlns:mns="witangowebservice">Error in soap request.No > soap request</mns:faultstring> > </env:Fault> > </env:Body> > > </env:Envelope> > > > At the same time, a look at the headers indicated for that request shows that > the content-type is erroneous and may be preventing a correct response: > > > > Date: Wed, 16 Mar 2011 15:05:40 GMT > Server: Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8l DAV/2 > Set-Cookie: Witango_UserReference=6E6DB37C755900C24D80D1C4; path=/ > Keep-Alive: timeout=5, max=100 > Connection: Keep-Alive > Transfer-Encoding: chunked > Content-Type: text/html > > 200 OK > When I use a WSDL editor (from Oxygen XML) to review the wsdl file ==> when I > test it, I get this error response > > > > "Invalid Content-Type:text/html. Is this an error message instead of a SOAP > response?" > > > > A further trip around the Google-verse appeared to indicate that content-type > has to be served up as text/xml in order for the webservice to work properly. > If an application does not specifically request that content-type, either > Witango or Apache is serving it up as text/html. I would think that the mime > type wws would take care of this, but apparently it is not. I tried tweaking > mime types in Apache to serve up wws as text/xml but that broke the mime type > for the Witango server for wws, so that wasn't the solution. > > > > What do I need to further configure on either the Apache side or the Witango > side to get the webservices served up as text/xml instead of text/html? > > > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. > > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
