Main Page | Packages | Class Hierarchy | Class List | Directories | File List | Class Members | Related Pages

org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget Class Reference

Inheritance diagram for org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget:

org.openmobileis.common.util.database.AbstractQueryManager org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget List of all members.

Detailed Description

Definition at line 56 of file MyCrmLeadsSynchroTarget.java.

Public Member Functions

 MyCrmLeadsSynchroTarget () throws ServiceException
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.
String getCollectionObjectId (Object obj)
SynchroAtomicObject[] getAllModifiedAtomicObjectSince (long date) 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.


Member Function Documentation

void org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.connect Credential  cred  )  throws UserNotFoundException, ServiceException
 

call at the beginning of the collection synchronisation.

Parameters:
cred : synchronisation credential
Exceptions:
UserNotFoundException 
ServiceException 

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 264 of file MyCrmLeadsSynchroTarget.java.

void org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.deleteCollectionObject String  id  )  throws OpenMSPException
 

Implement the delete part of the database.

Call by the synchro service when a object has been deleted on the terminal.

Parameters:
id is the identifiant of the deleted object.
Exceptions:
OpenMSPException :throws when there is a database delete problem. The synchro collection will be in error in the terminal synchro journal. The id will come back in the next synchronisation.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 179 of file MyCrmLeadsSynchroTarget.java.

void org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.disconnect  ) 
 

call at the end of the collection synchronisation.

Parameters:
cred : synchronisation credential
Exceptions:
UserNotFoundException 
ServiceException 

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 271 of file MyCrmLeadsSynchroTarget.java.

Array org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getAllCollectionObject  )  throws OpenMSPException
 

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.

Returns:
Return all the object of the collection for the user that initiate the collection.
Exceptions:
OpenMSPException : throws when there is a problem to invalidate the synchronisation. The synchro collection will be in error in the terminal synchro journal.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 207 of file MyCrmLeadsSynchroTarget.java.

References org.openmobileis.common.util.collection.Array.add(), org.openmobileis.common.util.collection.Array.get(), org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getCollectionObjectWithId(), and org.openmobileis.common.util.collection.Array.size.

SynchroAtomicObject [] org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getAllModifiedAtomicObjectSince long  date  )  throws OpenMSPException
 

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.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 239 of file MyCrmLeadsSynchroTarget.java.

String org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getCollectionName  ) 
 

Returns:
the name to the terminal FODB collection.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 119 of file MyCrmLeadsSynchroTarget.java.

Object org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.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.

Returns:
the collection object with the specified ID.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 126 of file MyCrmLeadsSynchroTarget.java.

References org.openmobileis.examples.mycrm.data.Leads.setAmount(), org.openmobileis.examples.mycrm.data.Leads.setCloseDate(), org.openmobileis.examples.mycrm.data.Leads.setDescription(), org.openmobileis.examples.mycrm.data.Leads.setIdaccount(), and org.openmobileis.examples.mycrm.data.Leads.setState().

Referenced by org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getAllCollectionObject().

SynchroConflicResolver org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.getConflicResolver  ) 
 

When a conflic is detected, the synchro service use this conflic resolver to determine the action to do.

We provide default conflic resolver behaviours.

See also:
org.openmobileis.synchro.algo.replication.AlwaysUpdateClientSynchroConflicResolver

org.openmobileis.synchro.algo.replication.AlwaysUpdateServerSynchroConflicResolver

Returns:
Return the conflic resolver use to manage synchro conflic.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 200 of file MyCrmLeadsSynchroTarget.java.

int org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.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.

If return -1 (default implementation) max row in not taken into account (ie always update file)

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 251 of file MyCrmLeadsSynchroTarget.java.

void org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.updateCollectionObject Object  obj  )  throws OpenMSPException
 

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.

Parameters:
obj is the instance of the modified object.
Exceptions:
OpenMSPException : throws when there is a database update problem. The synchro collection will be in error in the terminal synchro journal. The object will come back in the next synchronisation.

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 151 of file MyCrmLeadsSynchroTarget.java.

References org.openmobileis.examples.mycrm.data.Leads.getCloseDate(), org.openmobileis.examples.mycrm.data.Leads.getDescription(), org.openmobileis.examples.mycrm.data.Leads.getId(), org.openmobileis.examples.mycrm.data.Leads.getIdaccount(), and org.openmobileis.examples.mycrm.data.Leads.getState().

void org.openmobileis.examples.mycrm.data.jdbc.MyCrmLeadsSynchroTarget.updateSynchroDB FastObjectDB  db  )  throws OpenMSPException
 

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.

Parameters:
db the database collection (thedb contains only the synchronized collection).

Implements org.openmobileis.database.fastobjectdb.synchro.server.FODBSyncTarget.

Definition at line 258 of file MyCrmLeadsSynchroTarget.java.


The documentation for this class was generated from the following file:
Generated on Mon Jul 10 10:29:37 2006 for OpenMobileIS by  doxygen 1.4.4