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

MiG InfoCom AB
these events, making it a snap for you as a developer to use
DBConnect without almost any changes to the code. The events are
defined in the class
TimeSpanListEvent for activities and
CategoryStructureEvent for categories. They have the same
event types defined and are interpreted as follows:
CategoryStructureEvent/TimeSpanListEvent.ADDED
One or more activities/categories was added but usually not as a
result of a direct creation. It might be added from another source
where it was created for instance.
CategoryStructureEvent/ TimeSpanListEvent . REMOVED
One or more activities/categories was removed but usually not as a
result of a direct deletion. If might be removed because it no longer
was needed in memory for instance.
CategoryStructureEvent/ TimeSpanListEvent . EXCHANG
ED
An Activity or Category was exchanged for another one.
CategoryStructureEvent/ TimeSpanListEvent . ADDED_C
REATED
One or more activities/categories was added as a result of creation.
The creation part might for instance hint synchronizing tools that they
should add this to their database.
CategoryStructureEvent/ TimeSpanListEvent . REMOVED
_DELETED
One or more activities/categories was removed as a result of deletion.
The deletion part might for instance hint synchronizing tools that they
should remove this from their database.
Miscellaneous Topics
Logging
An important tool for troubleshooting and event tracking is the
logging build in to DBConnect. You can set any Logger object
on any of CategoryDepository
, ActivityDepository ,
DataSynchronizer (s), ConnectionProvider (s) or
DataProvider (s). This includes subclasses as well of course.
Almost any action in DBConnect and the depositories (which is
actually a part of the main MiG Calendar Component) are logged at
DBConnect Guide Page 16 / 25