From: Antti Villberg Date: Wed, 8 Mar 2017 14:50:59 +0000 (+0200) Subject: Import/export changes. A load. X-Git-Tag: v1.29.0~129 X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=commitdiff_plain;ds=sidebyside;h=9acebe9584f8f2a78f0322b6e0e24438e7ceb984;hp=9acebe9584f8f2a78f0322b6e0e24438e7ceb984;p=simantics%2Fplatform.git Import/export changes. A load. May cause some problems. Exports create Internals instead of blanks if possible. FixExportedOntology treatment now produces tgs that are compatible with Graph Compiler. Import creates L0.ExternalEntity instances for unresolved external references (thus making it fail safe). Note that addBuiltin("http://Projects") was removed from class CoreInitialization because its existence resulted in a non-functioning URI space because: * http://Projects was added as a "built-in resource" when the database is first initialized which means that ReadGraph.getResource("http://Projects") would succeed even when the resource was not yet properly imported from the project ontology * When the project ontology is imported, a new resource is created to represent http://Projects instead of using the existing uninitialized "built-in resource". The L0.ExternalEntity changes made to the standard transferable graph import in this patch caused the code to find the built-in resource for "http://Projects" and think that it has to be a resource that's already properly initialized. This led to the TG import not initializing the resource at all. Previously there was a bug here as well but it was hidden by the fact that the system would import the actual/new "http://Projects" resource from the ontology anyway. This effectively left the uninitialized built-in resource just hanging in the database as trash. refs #7016 Change-Id: I5d9dd8dea4df58cc54d4a6664c112a770ae7f7b3 ---