MiG InfoCom MiG Calendar DBConnect Guide - Manual (Page 8)

MiG InfoCom AB
collected into one PropertyMappingList object. To that
PropertyMappingList object are optionally also a special
update table associated that has its own, very simple,
UpdateMapping. One can also connect a number if mappings
to other tables in the form of IDToManyPropertyMappings.
These are for instance to map a single Activity to several
Categories though the use of a join table. Both of these features
are explained further below.
A DataProvider is wrapped around the
PropertyMappingList object and, for use with a database, a
ConnectionProvider are included as well. The
DataProvider has all the information on how to read/write
properties from the activities/categories and load/save it to a
backing store. For database persistence a DBDataProvider is
used and you can for instance use an XMLDataProvider to
read/write from an XML file (XML implementation not provided
with 1.0).
We must also add the more high level functionality of monitoring
the ActivityDepository and CategoryDepository as
well as provide background processing in a worker
thread/queue. This functionality is provided by the
DataSynchronizer which normally is an
ActivityDataSynchronizer or a
CategoryDataSynchronizer.
From that synchronizer you control almost every aspect of the
DBConnect plugin.
Layered Architecture
DBConnect is created in a layered architecture. You can choose
just to configure it or to add you own persistence delegates
instead of the ones provided by the plugin.
DBConnect Guide Page 8 / 25