MoreMotion Data Objects (ADOMs) |
![]() ![]() ![]() |
MoreMotion maintains hierarchically structured data objects called ADOM (Application Data Object Model). ADOMs are stored in memory in three scopes Application Scope An ADOM created in Application Scope is accessible by all the users of the web application and is kept memory as long as the web application runs unless it is removed explicitly. Session Scope Session ADOMs are accessible only by the current session. They can be preferred to accumulate session based temporary data, e.g. a Shopping Cart. The Session ADOMs are purged from memory when the session they are connected expires. Request Scope An ADOM created in Request Scope is accessible by the current request and it is removed from the memory when the request is responded by the MoreMotion.
MoreMotion API provides methods to create ADOMs and populate data in them. There are certain type of classes whose primary concern is to populate data in ADOMs by accessing to different sources. These type of classes are called Data Services. There are number of data service classes available in MoreMotion. Users can also developed their own Data Services by implementing MoreMotion's Data Service Interface. See Data Services. How an ADOM object is created Usually ADOMs are created by MoreMotion as an empty container and passed to the data service classes. The data service classes do not care about the name of the ADOM objects passed to them; they just insert the data they populated into them. There are cases that ADOM objects are created by the other Java classes using MoreMotion API. When this is the case, the class creates the ADOM and assigns a name to it as follows.
XML Representation of ADOM ''order'':
|