Mechanism to support orphaned and partially configured objects

Abstract

Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.

1 . A machine implemented method residing as executable instructions in a non-transitory computer-readable storage medium for execution on a processor, comprising:
 deploying, by the processor, an object to a project where the object includes configuration details that are delayed and defined at a later point in time;   presenting, by the processor the object to a first user in a first processing context and showing that first user the object lacking the configuration details; and   simultaneously presenting, by the processor, the object to a second user in a second processing context as a fully developed object with the configuration details configured in the object.   
     
     
         2 . The method of  claim 1  further comprising, interacting, by the processor, with a third user to apply selective aspects of the configuration details to a third processing context. 
     
     
         3 . The method of  claim 1  further comprising, allowing, by the processor, additional objects within the project to reference the object even in processing contexts where the object remains undefined with unapplied configuration details. 
     
     
         4 . The method of  claim 1 , wherein deploying further includes interactively receiving the configuration details from a third user. 
     
     
         5 . The method of  claim 1 , wherein deploying further includes integrating the object in an undefined state into the project. 
     
     
         6 . The method of  claim 1 , wherein permitting further includes presenting the object to the first user as a high-level object that is not activated. 
     
     
         7 . The method of  claim 1  further comprising, annotating, by the processor, the object to include specific details for deploying the object to the first processing context and the second processing context. 
     
     
         8 . A machine implemented method residing as executable instructions in a non-transitory computer-readable storage medium for execution on a processor, comprising:
 loading, by the processor, a first object within a project processing environment, the first object lacks a complete definition and the project processing environment includes a second object having a complete definition that references the first object;   configuring, by the processor, within the project processing environment a first version of the first object based on a first complete definition supplied by a first user;   configuring, by the processor, within the project processing environment a second version of the first object based on a second complete definition supplied by a second user; and   using, by the processor, within the project processing environment the first version of the first object to simulate first actions by the second user on the second object and using within the project processing environment the second version of the first object to simulate second actions by the first user on the second object.   
     
     
         9 . The method of  claim 8  further comprising, annotating, by the processor, a third object that defines details for moving the second object to a different processing environment. 
     
     
         10 . The method of  claim 9 , wherein annotating further includes using the details for moving the first version of the first object, the second version of the first object, and the second object to a different project. 
     
     
         11 . The method of  claim 8  further comprising, acquiring, by the processor, annotations for the second object that provides details for migrating the first object along with the first version and the second version of the first object to a different processing environment. 
     
     
         12 . The method of  claim 8  further comprising, receiving, by the processor, details for the first version and the second version of the first object in an interactive and piecemeal fashion from the first user and the second user. 
     
     
         13 . The method of  claim 8  further comprising, receiving, by the processor, the complete definition having alternative configurations for second object. 
     
     
         14 . The method of  claim 13 , wherein receiving further includes obtaining the complete definition over a lifecycle for a project associated with the project processing environment. 
     
     
         15 . A machine implemented method residing as executable instructions in a non-transitory computer-readable storage medium for execution on a processor, comprising:
 loading, by the processor, a first object to a project processing environment of a project that lacks configuration details and is deactivated, wherein a second object is active and includes a reference to the first object;   subsequently permitting, by the processor different versions of the first object to be dynamically instantiated within the project; and   simultaneously presenting, by the processor, the different versions of the first object to different users, wherein at least one version lacks the configuration details and is deactivated.   
     
     
         16 . The system of  claim 15  further comprising, acquiring, by the processor, a first version of the configuration details for a first version of the first object via annotations associated with the second object when the reference is attempted to be activated from the second object. 
     
     
         17 . The system of  claim 15  further comprising, acquiring, by the processor, at least one version of the configuration details by interacting with a particular user. 
     
     
         18 . The system of  claim 15  further comprising, processing, by the processor, the different versions of the first object to simulate different aspects of the second object. 
     
     
         19 . The system of  claim 15  further comprising, permitting, via the processor, the second object to execute in the project processing environment and acquire different versions of the configuration details for the first object in a piecemeal fashion and over a lifecycle of the project. 
     
     
         20 . The system of  claim 15  further comprising, acquiring, by the processor, annotations from the second object the annotations defining how to migrate the second object and the different versions of the first object to different projects and different project processing environments.