Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

BaSyx / Documentation / FileSystem Provider

< BaSyx ‎ | Documentation
Revision as of 04:55, 23 August 2019 by (Talk | contribs) (Created page with "{| class="wikitable" | Overview <nowiki>|</nowiki> HashMap provider <nowiki>|</no...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Overview | HashMap provider | Lambda provider | FileSystem provider | Implementation

The FileSystem provider is one of the basic providers in the BaSyx SDK for generic models. Each instance of the provider is based on an abstract FileSystem which is the local file system by default. Here, it is possible to provide own implementations of other types of file system, too. Like the HashMap provider and the Lambda provider, it is possible to store arbitrary object types in this provider. The key difference between FileSystem providers and other providers is that operations are not supported. Consider the following example:

	"name" : "MyElement",
	"data" : {
		"type" : "boolean",
		"value" : true
	"description" : {
		"de" : "Dies is ein beliebiges Objekt",
		"en" : "This is an arbitrary object"

The FileSystem provider serializes the content of each property and stores it in a file that is associated with the corresponding property path. The resulting file structure generated for the object by a FileSystem provider with the local root folder C:/root/ looks like this:

  • C:/root/name (file)
  • C:/root/data (directory)
    • C:/root/data/type (file)
    • C:/root/data/value (file)
  • C:/root/description (directory)
    • C:/root/description/de (file)
    • C:/root/description/en (file)

Back to the top