Had the same issue. I didnt find a solution but a workaround :/ ::
I wrapped the NSArray in a dictionary and override serialization for
dicts. If it is on of my ;array dicts' I serialize it' else I return
NULL.
to get the runtime to take over again, I use a WSProtocolHandler for
the subitems: That way I dont have to serialize the contents of the
array myself.
Hope that helps + my bad english didnt make it COMPLETELY
misunderstandable.
Regards,
Dominik
Am Dec 28, 2006 um 4:42 PM schrieb Josh Ferguson:
Hello list,
I'm trying to consume a .NET Document-Based SOAP web service using
WebServicesCore.framework. I've got almost everything working
except for
the way WebServicesCore serializes an NSArray. By default, an array is
serialized as so:
I tried writing my own custom serialization proc, but run into one
issue. How do I get the contextual information about the array? In
other
words, how do I know that the array is named "MyArray"? The
serialization proc receives three parameters: A pointer to the
WSMethodInvocationRef, a pointer to the actual object (CFArray/
NSArray),
and a pointer to the WSClientContext. I can't see how to get the
name of
the array out of any of this. In fact, the array name is a property of
the containing Dictionary, so I would need to know information
about the
dictionary that contains this array to be able to properly name it.
How
do I get around this? At this point in time I really wish I had gone
with a different SOAP client, as WebServicesCore is obviously meant
for
a very specific purpose (not consuming .NET web services). Any
information on how to work around this would be greatly appreciated!
