Databases
StackOverflow2013
Postsdbo
POGeneric WCF JSON Deserialization
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGeneric WCF JSON Deserialization
    primarykey
    data
    text
    <p>I am a bit new to WCF and will try to clearly describe what I am trying to do.</p> <p>I have a WCF webservice that uses JSON requests. I am doing fine sending/receiving JSON for the most part. For example, the following code works well and as expected.</p> <p>JSON sent:</p> <pre><code>{ "guy": {"FirstName":"Dave"} } </code></pre> <p>WCF:</p> <pre><code> [DataContract] public class SomeGuy { [DataMember] public string FirstName { get; set; } } [OperationContract] [WebInvoke(Method = "POST", BodyStyle = WebMessageBodyStyle.WrappedRequest, RequestFormat = WebMessageFormat.Json, ResponseFormat = WebMessageFormat.Json)] public string Register(SomeGuy guy) { return guy.FirstName; } </code></pre> <p>This returns a JSON object with "Dave" as expected. The problem is that I cannot always guarantee that the JSON I recieve will exactly match the members in my DataContract. For example, the JSON: </p> <pre><code>{ "guy": {"firstname":"Dave"} } </code></pre> <p>will not serialize correctly because the case does not match. guy.FirstName will be null. This behavior makes sense, but I don't really know how to get around this. Do I have to force the field names on the client or is there a way I can reconcile on the server side?</p> <p>A possibly related question: can I accept and serialize a generic JSON object into a StringDictionary or some kind of simple key value structure? So no matter what the field names are sent in the JSON, I can access names and values that have been sent to me? Right now, the only way I can read the data I'm receiving is if it exactly matches a predefined DataContract.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdavidmdem
    1. USdavidmdem
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGeneric WCF JSON Deserialization
      1. USdavidmdem
      1. VTFavorite
    2. VO
      singulars
      1. POGeneric WCF JSON Deserialization
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGeneric WCF JSON Deserialization
      1. USJimmy
      1. VTFavorite
    1. CO*Of course* you can guarantee that the json is conformant to the contract. Only if you don't have control of the client could you not be able to control it. If you don't have control of the client then it is probably outside the domain of your service and the point is moot. I don't see the problem. All the workarounds I see are futile and will just add pain. Read the specs on DataContract/DataMember and follow them. 2 pesos.
      singulars
      1. POGeneric WCF JSON Deserialization
      1. USSky Sanders
    2. COYou're right. Technically, I could write it into the JS before the info gets sent. And, I hinted in a different comment that this is probably what I will do in the end. Though, I would like a service to be able to handle an arbitrary number of fields that are not necessarily known beforehand. Does that make sense? I just want a service that can accept a completely arbitrary list of "key": "value" pairs and then decide what do do with them without having to know the "key" names beforehand.
      singulars
      1. POGeneric WCF JSON Deserialization
      1. USdavidmdem
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload