The mvsw Library
This mvsw library is organized as follows:
It builds its representation model on the two Rogue Wave® Server classes
IlsRepresentation and
IlsRpObject;
It provides a bridge to the Rogue Wave Views world through the class
IlsSwServerDataSource. This class inherits from the Rogue Wave Views class
IliDataGem. It instantiates graphical objects that are hidden at runtime. This Server data source can be described as a kind of Rogue Wave Views data source manager (see also
Server Data Sources vs. Views Data Sources and
Structure of a Server/Views .ilv File for more information).
The mapping offered by
mvsw is based on tables. There are three main classes:
IlsSwRepresentation IlsSwTable IlsSwRow The purpose of the mapping classes is to interface server objects with a set of Rogue Wave Views data sources. Server objects will be represented by rows in the tables that are associated with those Views data sources (see
Server/Views Classes Mapping Server Classes to Views Data Sources).
The role of each class can be illustrated as follows:
Server/Views Classes Mapping Server Classes to Views Data Sources
Important: A Views data source is in fact a kind of cursor on an underlying table. Therefore, most occurrences of the expression “Views data source” in this manual actually refer to its underlying table because as a rule, Rogue Wave Server representation objects use Views memory tables rather than their associated data sources. (See the Rogue Wave Views documentation for more information about data sources and their underlying tables.) |
This relationship is illustrated below.
Rogue Wave Views Memory Table and its Associated Data Source
To trap any event that can affect the contents of a data source (creation, deletion or modification of a row), a new type of memory table is used by the Server/Views library. This class is IlsSwMemoryTable which inherits from the Rogue Wave Views class IliMemoryTable. All the data sources used by an IlsSwTable object use an IlsSwMemoryTable table.
When you open a dynamic view based on the Server/Views representation model, a view is instantiated in the server. This view implements the following specifications from the view specification file you have designed using Rogue Wave Server Studio:
which server model objects you want to subscribe to;
how to represent these objects in the component;
how to map their attributes to representation object attributes.
Note: Within the context of the Server/Views mapping, a Server/Data Access view is an Rogue Wave Server dynamic view based on the Server/Views representation model. |
Version 6.3
Copyright © 2018, Rogue Wave Software, Inc. All Rights Reserved.