Anyone on this? On 09/ott/2014, at 15:52, Riccardo De Menna <[email protected]> wrote:
> Hi all, > > This is an ERRest specific question. > > I have an iOS -> WebObjects/ERRest setup regularly working. > One of the entities on both sides has an attribute that returns an > NSDictionary. > The problem is that when I try to update this attribute from the iOS side > into the WO side, it is silently skipped and left empty. > > The iOS side JSON-serializes everything before posting the Rest requests… as > a result, the dictionary attribute shows in the JSON output, very similar to > a relationship child node. > > I could be saying something stupid here so please don’t be too harsh… > > The thing is, together with any primitive type, I was assuming that the > Map/Dictionary kind was among the things I could “obviously” send. > Now I’m not so sure… could anybody shed some light on this, since I could be > banging my head under the wrong tree? > > In other words… Can I send a Map/Dictionary type object inside my JSON > request and hope that WO/ERRest will catch that it is NOT a relationship to > other nodes, but simply a plain old dictionary and call my entity setter or > am I simply confusing ERRest? > > BTW, not sure if it means anything, but the attribute is actually a class > method and not a real model attribute since the dictionary needs to be > processed. Could that be the issue? > > Please help, > Riccardo De Menna > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/demenna%40tuorlo.net > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
