Re: Witango-Talk: Simple SOAP instructions

Tue, 21 Jun 2005 21:56:39 -0700

When I run the taf to hit it, this throws a dom exception:

<@ASSIGN request$WebService "http://admin.bigheadtech.com/WhatsTheTime.wws">
<@ASSIGN request$SOAPAction "http://admin.bigheadtech.com/WhatsTheTime.wws">
<@ASSIGN request$SoapPayload '
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope">
<env:Body>
<mns:WhatsTheTime_Request xmlns:mns="witangowebservices" />
</env:Body>
</env:Envelope>
'>
<@ASSIGN Request$SOAPResponse '<@DOM VALUE="
<@URL
LOCATION='@@request$WebService'
USERAGENT='Witango <@VERSION> <@PLATFORM><@CRLF>Content-Type: text/xml<@CRLF>SOAPAction: "@@request$SOAPAction"'
POSTARGS='<?xml version="1.0" encoding="ISO-8859-1" ?><@CRLF><@VAR request$SoapPayload ENCODING="NONE">'
>">'>

Because the <@url is returning a page not found page.

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Jun 21, 2005, at 9:38 PM, Phil Wade wrote:

Correct on all counts.  The URL to the web service would also be http://www.mysite.com/myws.wws.

On 22/06/2005, at 2:31 PM, Robert Garcia wrote:


I understand that, and I assumed that the implementation was simplified, and that makes sense to implement a new feature.

So that I understand:

If I have a domain, www.mysite.com, and in the IIS setup, the root is F:\websites\mysite\

And the files are like so:

f:\websites\mysite\ws\myws.tcf
f:\websites\mysite\ws\myws.wsdl

URL to wsdl file would be: http://www.mysite.com/ws/myws.wsdl

Webservices ini:
[Webservices]
myws=

[myws]
webservice=ws/myws.tcf
wsdlfile=ws/myws.wsdl

SOAPAction to be hit, and set in the WSDL generator:

And of course the wws extension is listed in witango ini, and witangoevents.log verifies that ws is enabled, and that myws is registered. Also wws is mapped to w55 iis isapi dll.

This would be correct, right? The tcf doesn't need to be instantiated as an object or anything, correct?


-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Jun 21, 2005, at 9:11 PM, Phil Wade wrote:



Robert,

When the initial SOAP implementation was being architected there was a decisions made to simplify it as much as possible so it was decided that web services in its initial implementation they would be global to the server as tying them to domains.ini, objects.ini and applications.ini files would be an obstacle for those that did not use them and it became painful to configure and troubleshoot.  What we chose to do was to have the Witango server checks whether the service is defined (webservices.ini stanza) and make the call to the TCF by appending the current webroot taken from the SOAP request and append it to the path defined in the webservices.ini file.  The Stanza name is what defines the web service call and no path is required in the SOAP call itself (e.g.The sample add service is call with the URL http://127.0.0.1/AddService.wws).  The server then takes the webroot such as C:\InetPub\wwwroot\site1\ and appends it to the path in the webservice definition for the tcf and wsdl file.  This method was also chosen as in the future we will be able to expose a COM or JavaBean objects as a web service by simply defining it in the webservices.ini file and making a wsdl file to overlay onto it.

In a future release (6.x) we will be extending the implementation so that you will be able to define the application or domain that the webservice belongs to as well.


Phil


On 22/06/2005, at 8:06 AM, Robert Garcia wrote:




Thank you for the docs. I appreciate it.

I don't see anything in your documents different than what I did.... EXCEPT

You are using apache, and it looks like you are using a single domain type setup, with your webservices in the default htdocs location.

So maybe witango support could chime in on this. None of my sites use the default c:\inetpub\wwwroot location. Is that were the webservice files are expected to be? Does the webservice INI ignore the domain and webroot for a particular site? What file location is the webservices.ini expect to be the root, where these paths are relative to?

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Jun 21, 2005, at 2:11 PM, Matt Muro wrote:





<soap notes.doc>





________________________________________________________________________





________________________________________________________________________





________________________________________________________________________



________________________________________________________________________



________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to