Skip navigation links

Package fr.inria.atlanmod.neoemf.data.blueprints.config

Provides configuration classes to define specific behaviors of Blueprints data persistence.

See: Description

Package fr.inria.atlanmod.neoemf.data.blueprints.config Description

Provides configuration classes to define specific behaviors of Blueprints data persistence.

Configuration defined using the classes inside this package are usable for each Blueprints implementation. For backend-specific configuration refers to the corresponding package in the backend plugin.

This package defines the configuration by extending Config: BlueprintsTinkerConfig is a fluent API allowing to easily set Blueprints specific configuration in client applications. Since the configuration implements Config it can be used to combine Blueprints specific and generic configuration.

Configuration defined using the classes inside this package are usable for each Blueprints implementation. For backend-specific configuration refers to the corresponding package in the backend plugin (fr.inria.atlanmod.neoemf.data.blueprints.[backend]).

These classes are used to create option maps used in EMF save and load methods. For example, the following code creates a map that tells the framework to use a direct write approach (meaning that modifications are directly stored in the underlying database) and cache the accessed features to retrieve them efficiently. The direct write behavior is a Blueprints specific option, while the caching behavior is defined at the core level.


 // Create the option map
 Map<String, Object> options = new BlueprintsTinkerConfig()
     .cacheFeatures()
     .toMap();

 // Load the resource with the specified options
 myResource.load(options);

 // Manipulate the resource with a direct write approach and feature cache enabled
 myResource.getContents() [...]
 
Skip navigation links

Copyright © 2013–2019 Atlanmod. All rights reserved.