Objective-C/Cocoa is the dominant language/API for Apple’s OS X. Java is the dominant language for Web portals and other Internet services. So wouldn’t it make sense for these two technologies to talk to each other? Marcus Zarra walks you through a simple solution to get these two technologies communicating.
“Unfortunately, there is no SOAP API available for Objective-C that is as easy to use as Apache’s Axis.”
look at /Developer/Tools/WSMakeStubs
or the example
/Developer/Examples/Web Services/XMethodsInspector
Is there any support on Apple Developers site?
Neal Saferstein
http://developer.apple.com/
But i hope it was a joke. Everything is not well documented, but it is generally by choice, and sometimes due to a lack of interest from developers.
(Notice : you HAVE to like how the docs are written. i don’t)
The answer anyway, the whole communication protocol is bloated as hell. Ok given the fact that newer apis try to hide the implementation via annotations and other simplifications makes things bearable, but a good communication api, can and already lives without the bloat hell Soap simply is.
There are many and way better alternatives than SOAP ever will be.
I’m not really in the know on this stuff, but I think SOAP uses XML to conduct its transactions. What other APIs are there out there that do the same thing in the same manner with less bloat?
SOAP uses XML to conduct its transactions. What other APIs are there out there that do the same thing in the same manner with less bloat?
XML/RPC. The specification takes 3 pages and it’s straightforward to implement. And thus logically, implementations exists for most of the languages (I used it in Squeak/Smalltalk, Ruby, Objective-C, C, C++, Java…).
XML/RPC is not as “powerful” as SOAP, but it’s infinitely less bloated too 🙂 (and if you want simple remote rpc / distributed object capacities, XML/RPC is imho much better because simpler).
Is there any other technical resources othere than from Apple.com
Neal Safertein