WebServicesCore problem

Graham J Lee leeg at thaesofereode.info
Sat Feb 3 03:06:33 PST 2007


On 2 Feb 2007, at 17:57, Todd Ditchendorf wrote:

> [...]
>> as you can tell, I'm more used to doing:
>> NSLog(@"%@",(NSDictionary *)result);
>> but as this project is in C I can't use the toll-free bridging :- 
>> (.  So it looks like I'm missing something fundamental about  
>> CoreFoundation...question is, what is it?  :-)
>
> I'm thinking you're not actually accessing the service (is the url  
> correct?, etc). I would try coding it with TFB and Foundation  
> included just for kicks until you are certain it's working, then  
> slowly remove the cocoa code line by line, checking for problems  
> each step of the way. But then I'm way more comfortable in Cocoa  
> than CF, so who knows.

That at least got me to print out the dictionary...
Result:
{
     "/FaultCode" = -65794;
     "/FaultExtra" = {domain = 3; error = -9812; msg = "Stream  
Error"; };
     "/FaultString" = "/CFStreamFault";
     "/kWSResultIsFault" = 1;
}
I'm willing to bet this is a problem with the SSL certificate, as the  
WSMethodInvocationRef doesn't even appear to have generated any XML.   
Actually, I just thought of a way to test that...I have access to the  
same API (but no credentials) on a deployment system.  Connecting to  
that produces a different error, but one which shows that the  
transaction did actually occur.

Wow, so much hassle to find a configuration problem ;-)

Thanks for all your help,

Graham.



More information about the MacOSX-dev mailing list