https://bugzilla.novell.com/show_bug.cgi?id=384580
User [EMAIL PROTECTED] added comment https://bugzilla.novell.com/show_bug.cgi?id=384580#c384144 Summary: json serialization discrepancy Product: Mono: Class Libraries Version: SVN Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Sys.Web AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [email protected] Found By: --- Hello, After the fix for item #384144, my application is now breaking in a new way, and I am not sure if this is by design as part of the updates to the ajax components, or if this is a regression. This worked with a version of mono from a month or two ago without issue. In my application's javascript code, it uses a generated proxy to make a call against a custom webservice that returns a list of things: IList<MyType>. Previously, when this was serialized, it would result in a json response that consisted of an array of objects. However, now the response comes back with a wrapper object that contains an array of objects (with the array name of 'd'). For example, with the original working code, if the return from the webservice was named 'result' in order to access the items of the returned list, I could just use result[i]. However, with the new set of code, I would need to access this as result.d[i]. I've had a difficult time finding concrete info on how these things should be serialized, and was working primarily off what I saw go across the wire, so apologies if this is now correct behavior. Is this a regression? Thanks, Mike -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
