[Mono-bugs] [Bug 384580] New: json serialization discrepancy

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Apr 28 21:51:59 EDT 2008


User mmorano at mikeandwan.us added comment

           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: mhabersack at novell.com
        ReportedBy: mmorano at mikeandwan.us
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


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?


Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list