Extending virtual member manager functionality in your application
The virtual member manager model extension framework enables you to extend the virtual member manager model both at deployment time and at runtime.
Although virtual member manager comes with a built-in model, you might need to add new property definitions, new entity types and new control types to satisfy your specific needs.
The format (model) of the
data graph can be expressed either as a dynamic model (XSD) or a static model
(statically-generated code).
Note: Properties
and entities in the same name space must be either all in the static model
or all in the dynamic model. The models cannot be mixed in the same name space.
The scope of extension includes adding at runtime and at deployment time.
Virtual member manager is based on Service Data Object (SDO). The virtual
member manager data graph model can be either static or dynamic. Static means
code has been generated at deployment time to implement the model; dynamic
means no code has been generated and the model is built in memory by loading
from XSD files during each startup.
Note: The performance of the static model
is better but the dynamic model is more flexible.
The virtual member manager model extension framework supports the following scenarios where virtual member manager is configured to use:
- the dynamic model and you need to create new property types for the virtual member manager built-in entity types at runtime through the virtual member manager API.
- the dynamic model and you need to create new entity types and their associated new property types at runtime through the virtual member manager API.
- the dynamic model and you need to create new property types for the virtual member manager built-in entity types at deployment time.
- the dynamic model and you need to create new entity types and their associated new property types at deployment time.
- the dynamic model and you need to create control types at deployment time.
- the static model and you need to create new entity types and their associated new property types at runtime through the virtual member manager API.
- the static model and you need to create new property types for the virtual member manager built-in entity types at deployment time.
- the static model and you need to create new entity types and their associated new property types at deployment time.
- the static model and you need to create control types at deployment time.