In general, Cache web services are meant to interoperate with all web service clients that are W3C standards compliant. In addition, we have added support for the Microsoft proprietary XML dataset format.
Cache web service support works with the clients that we've tested. I'm sure the Mac support works with most web services. A generalization cannot be made about what is happening here. The specific interoperability issue needs to be addressed. I would suggest calling Cache support with the specifics of the problem and how to reproduce it. As a further note, the Cache web service test page is just that - a test page. It is just a way to display the XML response message and does not use the same HTTP headers as a real SOAP request. Marvin "Jens Eliasson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Thanks for your help Marvin. I checked the link but haven't tested the > tools yet, they're all PC-stuff (which gives me the creeps). I've gone > far enough working with Cach�-Studio in Virtual PC. There are quite a > few tools of this kind on the mac too. > > Well, the true reason is that I don't really have the time to analyse > the problem now. So I will do a quick-and-dirty with strait http upload > first. If I have to I will go on along the previous path later on. > > But I added a OnPreHTTP and managed to save most of the values from % > request into a global. And when I compare the values from the calls ( > WebService test page and from the Mac), there are some striking > differences. For instance that the test page makes a HTTP-GET while the > web service client on the Mac makes a HTTP-POST. And when I test a > number of public web services from the Mac (especially at http://www. > xmethods.net), it works perfectly. Then I just configure the call > according to the WSDL and run it without any problems. > > This make me suspicious about the web services in Cach�. Is really > working according to W3C-guidelines or is it all done for .NET? > > I'm also critical to Apple where it is due. The web services client on > the Mac is called WebServicesCore and it is very high level, which is > part of the problem. Their documentation about it is also not very good. > But since it works fine in other cases I still think the problem is in > Cach�. > > /Jens > > In <[EMAIL PROTECTED]> Marvin Tener wrote: > > For viewing the SOAP messages for debugging, take a look at > > http://www.pocketsoap.com. They have two free products tcpTrace and > > proxyTrace. > > > > Marvin > > > > "Jens Eliasson" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > >> I've been working with Cach� for some time, but now is my first time > >> to try make a web service to work. > >> > >> The problem does not really seem to be on the server-side. I'm trying > >> to make it work with Mac OS X being the client, but get a "Badly > >> formed SOAP message" whatever I do. The web service works as supposed > >> from the test page, but I don't have a clue if that means that it > >> really should work from a client computer, since it's all done in csp. > >> > >> Best if somebody have experience of using the "call soap" AppleEvent > >> from Mac OS X, that can tell me how to do it right strait away ( > >> doesn't seem likely)? > >> > >> Is it possible to intercept the service in some way and save the > >> complete SOAP-request? That way I imagine that the work of actually > >> making it work is a simple matter. > >> > >> Now im running: Cache for Windows NT (Intel) 5.0.4 (Build 829U) > >> > >> Thanks/ > >> Jens @ Headlong Development AB
