Okay,
This workaround seems to work. On the server side I put my array
elements in as keys for a WOStringKeyMap and modified the client to
get the result array back out via allKeys().
This is a huge problem however as every service, including EOs that
contain arrays, would need methods changed/wrapped to return
WOStringKeyMap instead of arrays, and this of course would have to be
done for both the server and client applications.
Does anybody know if Apple has a prioritization on getting this fixed?
From what I can tell so far this basically makes WO5.4/5.4.1
unusable as a web services consumer (unless of course you never need
to use arrays).
- mike
On Feb 25, 2008, at 1:41 PM, Art Isbell wrote:
On Feb 25, 2008, at 9:09 AM, Michael DeMan wrote:
Does anybody know if the item noted on the posting below is fixed
in 5.4.1, and if not, could anybody describe the workaround?
http://www.mail-archive.com/[email protected]/
msg15103.html
It is apparently not fixed in 5.4.1.
A workaround would be to rewrite each Web service method that
returns NSArray to return WOStringKeyMap. Each Web service client
would then need to extract the array from the WOStringKeyMap. Not
ideal, but this should work.
Aloha,
Art
_______________________________________________
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]
