We've gotten webservices running under both the Witango 5.5 server
and also the J2EE Witango servlet...
It IS tricky in terms of setting the paths, but we did get that
worked out, and once done, it worked "as advertised".
I have asked my programmer who did this to check in on this issue.
On Jun 21, 2005, at 2:11 PM, Robert Garcia wrote:
Before I write out a detailed email to support, has anyone
successfully gotten the new Webservices to work?
I have built everything starting with the tutorial, and the
events.log confirms that webservices are enabled, and that the ws
is registered, and I have set the wws extension mapping in IIS. But
when I use the taf example to hit the wws, I just get page missing.
Also, I am using special SOAP class in Realbasic to hit, and it
loads the wsdl ok, but can find the action when hitting. I know it
works, cuz there are sample webservices out there made by .NET that
you can test on.
I also built my own HTTP tester to hit the wws, and wrote the taf
as in the documentation, all can find the action/url.
I made the example EXACTLY as tutorial, except not localhost. Only
difference is I am using a domain, admin.bigheadtech.com.
Some questions
In the example, the webservices.ini uses relative paths to point to
the wsdl and tcf files. What is this relative too? Is this relative
to the webroot for the given VIRTUAL website in IIS? Is this
supposed to be relative to some other point?
Does this mean that with this structure, the wws is ALWAYS going to
be at the root level of the site? so even though as in example, the
tcf and wsdl is at webservices/WhatsTheTime/WhatsTheTime.tcf, it
will be called by SOAPAction http://www.mysite.com/WhatsTheTime.wws ?
Since I have many domains in IIS, all with different webroots, how
does the witango wws system handle this? I think I read all the
docs I could get my hands on, any help would be appreciated.
I am looking forward to getting this working, we have written many
webservices with Witango and RB, but it was a tough process due to
the limitations in witango v5. We basically rolled our own, and
couldn't even use the DOM, cuz it didn't always handle CDATA
sections correctly, and other types. Plus, there was the issue of
encoding, v5 only able to result ISO 8559 encoding and not UTF-8.
--
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
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
