Documentation:JsonToObject vs Tajson: Difference between revisions

JsonToObject vs Tajson

Revision as of 06:17, 22 February 2023

This page was created by Hans.karlsen@mdriven.net on 2020-01-27. Last edited by Stephanie@mdriven.net 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 offers 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 creates new objects.

@@ Line 1: / Line 1: @@
-selfVM.JsonToObjects as described here [[Import xml and JSon with MDriven]] is available only in Viewodel 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).
+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 offers no transformation layer between your Json and your model - things need to share names in order to match.
+JSonToObjects offers no transformation layer between your Json and your model - things need to share names to match.
-The [[Tajson|TaJSon]] strategy is different in that it always use a viewmodel as a template for both getting and setting data hierarchies to and from json strings. TaJson offers to update objects hieracies in a whole other way than JSonToObjects does as JSonToObjects always create new objects.
+The [[Tajson|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 creates new objects.
 [[Category:View Model]]

Revision as of 06:17, 22 February 2023

Before connecting to our staff