Documentation:JsonToObject vs Tajson: Difference between revisions

JsonToObject vs Tajson

Latest revision as of 05:57, 27 January 2025

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 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.

@@ Line 1: / Line 1: @@
 <message>Write the content here to display this box</message>
-<code><span class="col-black">'''selfVM.JsonToObjects'''</span></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><span class="col-black">'''selfVM.JsonToObjects'''</span></code> as described here - [[Documentation:Import xml and JSon with MDriven|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|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.
+The [[Documentation: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 create new objects.
 [[Category:View Model]]
 {{Edited|July|12|2025}}