I wrote a version of jQuery.deserialize that supports serialized data generated from the serialize, serializeArray and serializeObject functions. It also supports all form element types, including checkboxes and radio buttons.
Here is an example using CustomCreationConverter. public class JsonItemConverter : Newtonsoft.Json.Converters.CustomCreationConverter<Item> { public override Item Create(Type objectType) { throw new NotImplementedException(); } public Item Create(Type objectType, JObject jObject) { var type = (string)jObject.Property(“valueType”); switch (type) { case “int”: return new IntItem(); case “string”: return new StringItem(); } throw new ApplicationException(String.Format(“The given vehicle type {0} is … Read more
What I don’t understand, does the annotation affect the de/serialization itself No. Its retention is ‘source’, so it’s discarded after compilation. The bytecode will contain no trace of it. It has no way to influence runtime behaviour (besides possibly compile-time code generation, which does not happen). Like @Override, it is optional and is supposed to … Read more
After constructing JavaType, both call same deserialization functionality, so the only difference is the way generic type is handled. Second one is fully static, so type must be known in compile type, and can not vary. So it is similar to using basic Class literal. First one is dynamic, so it can be used to … Read more
You can try this: dynamic task = JObject.Parse(rawJson); Documentation: Querying JSON with dynamic
It looks like the problem is that you are getting incompatible versions of jackson-core and jackson-databind – jackson-core 2.0.5 is being pulled in, but I believe at least 2.1.0 is required. The first line of the exception tells you that it can’t find the method JsonParser.getValueAsString(), looking at the API docs for 2.0.5, that method … Read more
Ollie’s answer is definitely the best way to go for this case, but it does push some knowledge into the caller, which may be undesirable. It also isn’t very flexible. I still think it’s a great answer and exactly what you want here, but this is a nice simple example to explore custom structural encoding. … Read more
I found a way to convert all nested objects to Dictionary<string,object> by providing a CustomCreationConverter implementation: class MyConverter : CustomCreationConverter<IDictionary<string, object>> { public override IDictionary<string, object> Create(Type objectType) { return new Dictionary<string, object>(); } public override bool CanConvert(Type objectType) { // in addition to handling IDictionary<string, object> // we want to handle the deserialization of … Read more
This should work… JavaScriptSerializer ser = new JavaScriptSerializer(); var records = new ser.Deserialize<List<Record>>(jsonData); public class Person { public string Name; public int Age; public string Location; } public class Record { public Person record; }
You may want to try this. string xml = @”<Students> <Student ID=””100″”> <Name>Arul</Name> <Mark>90</Mark> </Student> <Student> <Name>Arul2</Name> <Mark>80</Mark> </Student> </Students>”; dynamic students = DynamicXml.Parse(xml); var id = students.Student[0].ID; var name1 = students.Student[1].Name; foreach(var std in students.Student) { Console.WriteLine(std.Mark); } public class DynamicXml : DynamicObject { XElement _root; private DynamicXml(XElement root) { _root = root; } … Read more