Documentation:JsonToObject vs Tajson: Difference between revisions

JsonToObject vs Tajson

Revision as of 08:38, 15 December 2022

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

JSonToObjects offers no transformation layer between your Json and your model - things need to share names in order to match.

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

This page was edited 99 days ago on 02/10/2024. What links here

Revision as of 13:04, 27 January 2020 (view source) Hans Karlsen (talk \| contribs) (Created page with "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 an...") Tag: Visual edit		Revision as of 08:38, 15 December 2022 (view source) Stephanie Namugambe (talk \| contribs) No edit summary Tag: Visual edit Newer edit →
Line 4:		Line 4:

	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 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.
			[[Category:View Model]]