Mechanisms to persist hierarchical object relations
View Patent ↗Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.
1. A method, comprising:
acquiring, by an object relationship service represented as executable instructions that execute on a processor, unique identifiers for objects from a project schema of a project, each object having a specific unique identifier, and identifying each object as instructions for a particular software module that is processed with the project;
maintaining, by the object relationship service, a mapping that represents hard-coded hierarchical relationships between the objects defined in the project schema;
removing, by the object relationship service, the hardcoded hierarchical relationships in the schema and the objects;
creating, by the object relationship service, directories and files within those directories uniquely representing the objects and the mapping with each container object stored in a unique directory named with that container's unique identifier and each object stored in a unique file named with that object's unique identifier;
organizing, by the object relationship service, the directories and files into a storage organization that represents the mapping; and
managing, by the object relationship service, the objects and the mapping for the project through loading of the objects from the directories and files into memory recreating the mapping and through writing changes made the objects into corresponding ones of the directories and the files as a modified storage organization reflecting any changes to the mapping.
2. The method of claim 1 , wherein acquiring further includes randomly generating each of the unique identifiers.
3. The method of claim 2 , wherein randomly generating further includes randomly producing each identifier to a predefined length selected from a predefined set of character sets.
4. The method of claim 1 further comprising, rendering, by the object relationship service, the project and the mapping in a graphical user interface presentation format.
5. The method of claim 1 further comprising, searching by the object relationship service, the storage organization for one or more particular objects as one or more particular files based on a supplied hierarchical relationship used by a user as a search.
6. The method of claim 1 , wherein retaining further includes preventing details associated with the hierarchical relationships from being stored within the files or the objects.
7. A method, comprising:
identifying, by a project relationship manager represented as executable instructions that execute on a processor, unique identifiers for objects of a project, and identifying each object as instructions that are executed by the processor;
organizing, by the project relationship manager, a storage organization for the objects that maintains and represents hierarchical relationships between the objects using the unique identifiers without using any hardcoded references maintained for and with the objects or with a project schema for the project during execution of the objects when processing the project by creating folders and files within the storage organization utilizing the unique identifiers as folders and files within the folders and the hierarchical relationships derived from the storage organization;
loading, by the project relationship manager, the files from memory recreating the hierarchical relationships from the storage organization into the memory when the project is loaded for processing; and
writing, by the project relationship manager, any changes made to the hierarchical relationships during processing of the project from the memory to corresponding ones of the folders and the files in a modified storage organization.
8. The method of claim 7 , wherein identifying further includes generating each of the unique identifiers.
9. The method of claim 7 further comprising, searching, by the processor, the storage organization using a particular unique identifier to discover particular hierarchical relationships for a particular object associated with the particular identifier.
10. The method of claim 7 further comprising, searching, by the project relationship manager, the storage organization for a particular hierarchical relationship to discover particular unique identifiers for particular objects associated with the particular hierarchical relationship.
11. The method of claim 7 further comprising, presenting, by the project relationship manager, the hierarchical relationships of the objects on a display associated with the processor.
12. The method of claim 10 , wherein presenting further includes providing the presentation within a graphical user interface.
13. A system, comprising:
a non-transitory storage medium representing storage of a file system; and
a storage manager operable to:
(i) execute on a processor;
(ii) organize the storage in a storage organization as created files within the storage using a mapping that is derived from hardcoded relationships defined in a schema for objects of a project and derived from the objects, wherein the mapping is based on naming the files with unique identifiers for each of the objects and storing the files in the storage organization;
(iii) load the files as the objects into memory and recreate the mapping defining the hardcoded relationships when the project is loaded into memory for processing; and
(iv) write any changes made in the mapping during processing of the project from the memory into corresponding ones of files in a modified storage organization within the storage.
14. The system of claim 13 , wherein the storage manager is further operable to (v) search the storage using a name for a particular object and return a reference to at least one particular hierarchical relationship for that particular object.
15. The system of claim 13 , wherein the storage manager is further operable to (v) search the storage using a name for a particular hierarchical relationship and return a reference to at least one particular object associated with that particular hierarchical relationship.
16. The system of claim 13 , wherein the storage manager is further operable to (v) derive a graphical presentation for presentation on a display associated with the processor that graphically depicts the objects and the mapping.