MECHANISMS TO SUPPORT MULTIPLE NAME SPACE AWARE PROJECTS

• US 20100036870A1
• Filed: 08/05/2008
• Published: 02/11/2010
• Est. Priority Date: 08/05/2008
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Lowry, Lee Edward, Carter, Stephen R., Street, William, Thurgood, Brent, Scheuber-Heinz, Volker Gunnar, Cox, Ryan, Vasudevan, Rajesh
• Granted Patent: US 8,341,190 B2
• Time in Patent Office: Days
• US Class Current: N/A
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/20 Software design

Abstract

Mechanisms to support multiple name space aware projects are provided. Multiple roots of a project declare multiple namespacing mechanisms. Resources of the project can utilize each of the multiple namespacing mechanisms. In some cases, a particular resource of the project can override and use a foreign namespace that is associated with a different project hierarchy even while that particular resource resides within a project hierarchy associated with the original project and even while the project hierarchy does not declare, at the root, the foreign namespace.

Claims

1. A method for supporting multiple namespaces, comprising:

recognizing at a root of a project hierarchy a first namespace root object declaration;

recognizing a second namespace root object declaration;

supporting first objects declared under the first namespace root object declaration of the project hierarchy within a first namespace; and

supporting second objects declared under the second namespace root object declaration of the project hierarchy within a second namespace.

2. The method of claim 1 further comprising, maintaining the first namespace root object declaration and the second namespace root object declaration as separate independent containers for storage and retrieval of the first objects and second objects within the project hierarchy.

3. The method of claim 1 further comprising, identifying a particular first object that declares a foreign namespace that is different from the first namespace and the second namespace and that is associated with a different project hierarchy and a different project.

4. The method of claim 3 further comprising, dynamically deploying the particular first object to the foreign namespace via a foreign namespace specification that provides a mechanism for deployment to the foreign namespace.

5. The method of claim 1, wherein recognizing the second namespace root object declaration further includes permitting the second namespace root object declaration to be referenced and declared within the project hierarchy as a second project having a different project hierarchy from the project hierarchy and having the second namespace.

6. The method of claim 1 further comprising, storing content data associated with the first objects and the second objects in a repository that is independent of the first namespace and the second namespace and dynamically using a first namespace specification and a second namespace specification to render the content data, when accessed during the lifecycle of a project, to the first and second namespaces from the repository.

7. The method of claim 1 further comprising, managing the first objects as a first sub-project hierarchy within the project hierarchy and the second objects as a second sub-project hierarchy within the project hierarchy, wherein structure is shared within the project hierarchy but the first and second namespaces are different from one another.

8. A machine implemented method, comprising:

parsing a project hierarchy to load resources to a processing environment;

deploying first resources from the project hierarchy to the processing environment in a first namespace; and

deploying second resources from the project hierarchy to the processing environment in a second namespace.

9. The method of claim 8, wherein parsing further includes identifying the first resources as those resources that are declared following a first namespace root object declaration within the project hierarchy.

10. The method of claim 9, wherein parsing further includes identifying the second resources as those resources that are declared following a second namespace root object declaration within the project hierarchy.

11. The method of claim 8, wherein parsing further includes identifying third resources within the project hierarchy associated with a different project hierarchy and a third namespace.

12. The method of claim 11 further comprising, establishing a reference to the different project hierarchy within a different processing environment and requesting that the third resources be deployed within the third namespace.

13. The method of claim 8, wherein parsing further includes identifying the second namespace as a root reference to a different project hierarchy that uses the second namespace.

14. The method of claim 8 further comprising, dynamically deploying the second resources to the first namespace when during a lifecycle of a project associated with the project hierarchy, the second resources are copied or moved from the second namespace to the first namespace within the project hierarchy.

15. A machine-implemented system, comprising:

a project model implemented in a machine-accessible and computer-readable storage medium and accessible to services that process on a machine of a network; and

a generic project manager implemented in a machine-accessible and computer-readable storage medium and to process on the machine or a different machine of the network;

wherein the project model is organized as an object hierarchy, each object representing a resource of a project, and wherein multiple namespaces are declared as objects within the object hierarchy and the generic project manager selectively loads the resources to the multiple namespaces in response to the object hierarchy.

16. The system of claim 15, wherein at least one object is defined within the object hierarchy as a reference to a different project model having a different object hierarchy and associated with a particular namespace.

17. The system of claim 15, wherein particular resources associated with a particular namespace are declared within the object hierarchy following a particular object.

18. The system of claim 15, wherein the generic project manager permits each resource defined within the object hierarchy to override its namespace assignment.

19. The system of claim 15, wherein the generic project manager requests an external generic project manager to deploy a particular resource to a particular namespace when that particular resource borrows structure and the particular namespace from a different project model associated with a different object hierarchy.

20. The system of claim 15, wherein the generic project manager uses translation utilities to permit each of the resources to be moved and used between the multiple namespaces within the object hierarchy.

21. A machine-implemented system, comprising:

a first object hierarchy implemented in a machine-accessible and computer-readable storage medium that defines a first project;

a second object hierarchy implemented in a machine-accessible and computer-readable storage medium that defines a second project; and

a namespace aware service implemented in a machine-accessible and computer-readable storage medium and to process on a machine of a network;

wherein the namespace aware service permits first objects associated with the first hierarchy of the first project to deploy and use multiple namespaces, and wherein the namespace aware service also permits selective first objects of the first hierarchy to borrow structure from other namespaces associated with the second hierarchy of the second project.

22. The system of claim 21, wherein some of the first objects include namespace overrides that force the namespace aware service to deploy those first objects to a specific namespace defined by the namespace overrides.

23. The system of claim 21, wherein a particular namespace for a particular first object is resolved by the namespace aware service by a location of a definition for the particular first object within the first object hierarchy.

24. The system of claim 21, wherein the first object hierarchy includes objects that define each of the multiple namespaces.

25. The system of claim 21, wherein the namespace aware service utilizes namespace specifications to deploy the first objects to each of the multiple namespaces.