Inheritance diagram for org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget:
This target act has a database connector for the synchro service. To specify the temp directory where generated db file (during complete synchronisation) is use the property :org.openmobileis.database.fastobjectdb.synchro.server.generateddb.installpath
Definition at line 44 of file FODBSyncTarget.java.
Public Member Functions | |
String | getCollectionName () |
Object | getCollectionObjectWithId (String id) throws OpenMSPException |
It is use by the synchro service to get an object from the database when it has to be updated on the terminal. | |
void | updateCollectionObject (Object obj) throws OpenMSPException |
Implement the update part of the database. | |
void | deleteCollectionObject (String id) throws OpenMSPException |
Implement the delete part of the database. | |
SynchroConflicResolver | getConflicResolver () |
When a conflic is detected, the synchro service use this conflic resolver to determine the action to do. | |
Array | getAllCollectionObject () throws OpenMSPException |
It's call when a complete synchronisation is done to fill the terminal database with all object. | |
SynchroAtomicObject[] | getAllModifiedAtomicObjectSince (long syncnumber) throws OpenMSPException |
Return all atomic object uid modified since specified syncnumber. | |
int | getUpdateMaxNbRow () |
Return the max number of row that update file can contains If more than max row must be updated on the PDA, a complete synchronisation will be started, the database file will be send. | |
void | updateSynchroDB (FastObjectDB db) throws OpenMSPException |
call by synchronisation service during complete synchronisation to update the generated db collection. | |
void | connect (Credential cred) throws UserNotFoundException, ServiceException |
call at the beginning of the collection synchronisation. | |
void | disconnect () |
call at the end of the collection synchronisation. |
|
call at the beginning of the collection synchronisation.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.connect(). |
|
Implement the delete part of the database. Call by the synchro service when a object has been deleted on the terminal.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.deleteTargetForSynchroObjectId(). |
|
call at the end of the collection synchronisation.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.disconnect(). |
|
It's call when a complete synchronisation is done to fill the terminal database with all object. If no complete synchronisation can occurs (getUpdateMaxNbRow() always return -1), the method is never call. So no implementation is needed. Complete synchronisation is a convenient way to optimize the terminal synchronisation. some time it's make less time to generate the Terminal complete collection on the server side than to synchronize all modifications.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. |
|
Return all atomic object uid modified since specified syncnumber. Syncnumber is a number incremented for each synchro request. It can be converted to a timestamp with the SyncNumberManager. It's preferable to use number increment for synchronisation than timestamp to avoid desynchronized clock problem. Terminal and server can be desynchronized at the system cloc level of a few second. A synchronisation can elapse less than a few second. This can leads to synchronisation problem that can be difficult to track. Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.getAllModifiedAtomicObjectSince(). |
|
|
It is use by the synchro service to get an object from the database when it has to be updated on the terminal.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.getTargetObjectWithId(). |
|
When a conflic is detected, the synchro service use this conflic resolver to determine the action to do. We provide default conflic resolver behaviours.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.getSynchroConflicResolver(). |
|
Return the max number of row that update file can contains If more than max row must be updated on the PDA, a complete synchronisation will be started, the database file will be send. If return -1 (default implementation) max row in not taken into account (ie always update file) Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.getUpdateMaxNbRow(). |
|
Implement the update part of the database. Call by the synchro service when a object has been modified on the terminal. There's only an update method, no insert because on the server side we can't know if it's an update on an insert. Because of synchronisation problems, a created object on the terminal can be synchronized two time. So for each modified object on the terminal you have to validate if it's already exist.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. Referenced by org.openmobileis.database.fastobjectdb.synchro.server.FODBOpenMSPSynchroTargetWrapper.updateTargetWithSynchroObject(). |
|
call by synchronisation service during complete synchronisation to update the generated db collection. Use to modifiy db objects before the db files are send to the Terminal. Empty is nothing has to ne done.
Implemented in org.openmobileis.database.fastobjectdb.db.test.TestFODBSyncTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmAccountSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLabelSynchroTarget, org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget, org.openmobileis.examples.server.synchro.BaseDataFODBSyncTarget, and org.openmobileis.modules.crm.database.common.jdbc.JDBCTerminalUserFODBSyncTarget. |