JsonToObject vs Tajson
(Adding message template to the top of the page) |
(Replacing message template with parser tag) |
||
| Line 1: | Line 1: | ||
<message>Write the content here to display this box</message> | |||
<code>selfVM.JsonToObjects</code> as described here - [[Import xml and JSon with MDriven]] - is available only in ViewModel and will import json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent-in type (first argument). | <code>selfVM.JsonToObjects</code> as described here - [[Import xml and JSon with MDriven]] - is available only in ViewModel and will import json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent-in type (first argument). | ||
Revision as of 07:44, 17 June 2024
This page was created by Hans.karlsen on 2020-01-27. Last edited by Stephanie on 2025-01-27.
selfVM.JsonToObjects as described here - Import xml and JSon with MDriven - is available only in ViewModel and will import json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent-in type (first argument).
JSonToObjects offer no transformation layer between your Json and your model - things need to share names to match.
The TaJSon strategy is different in that it always uses a ViewModel as a template for both getting and setting data hierarchies to and from json strings. TaJson offers to update object hierarchies in a whole other way than JSonToObjects do as JSonToObjects always create new objects.