Hello Jesse;
Some of these issues I have written about on the WO wiki and it is
possible that some or all of these problems could be worked through
given enough time and effort. The "inability to deserialise
temporary GIDs" was the tipping point when I decided that this was
consuming more resource than writing my own RPC with which I would
have complete control of the server and the client architecture for
my purposes.
These are the issues that I experienced;
* fixing the WSDL URL-generation in a servlet container - had to
create my own handler to do this
* lack of documentation about EO serialisation - had to figure this
out myself through experimentation
* inability of WebServicesCore to handle multi-refs - had to disable
this on the WO end, took a while to figure out.
* Inability to serialise nil in WebServicesCore
* problems for WebServicesCore to deserialise timestamps with a
millisecond component
* inability to deserialise temporary GIDs
cheers.
I'd be interested to know more about the kinds of problems you had
and what threshold lead you to change your approach -
...
i have to talk to a webserver (undecided so far if xml-rpc or
soap) from a cocoa application
my goals are:
...
Have a look at "WebServicesCore" which is a native framework from
Apple included in MacOS-X for doing SOAP from the likes of Cocoa.
I worked with this for a while and then dropped it owing to
various problems I had with it once my requirements became more
demanding. From there I rolled my own JSON-RPC infrastructure.
Compared to trying to get SOAP working properly, writing my own
JSON-RPC system proved *much* better for me.
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
