com.srv4pos.server.api.sync.sample

Class CategorySyncAdapter

java.lang.Object

com.srv4pos.server.api.sync.sample.CategorySyncAdapter

All Implemented Interfaces:

EntitySyncAdapter<CategoryInfo>

public class CategorySyncAdapter
extends Object
implements EntitySyncAdapter<CategoryInfo>

Field Summary

Fields

Modifier and Type	Field and Description
private MemoryLocalStorage	storage

Constructor Summary

Constructors

Constructor and Description
CategorySyncAdapter(MemoryLocalStorage storage)

Method Summary

Modifier and Type	Method and Description
void	createOrUpdateEntityFromInfo(CategoryInfo info) Method should update corresponding entity from info (entity could be located by identifier from info) or create entity if client has no entity with such identifier.
private void	doUpload(Uploader<CategoryInfo> uploader, SyncCategory cat)
void	upload(Uploader<CategoryInfo> uploader) Method should process all not synced entities from local storage: convert each entity to Info pass each Info to uploader.upload - it will take care about posting info to server if uploader returned new identifier for item, store it to local entity (that means entity is new and was created on server with new identifier) mark uploaded entity as synced (to not sync it again until it will be changed) store updated entity to local db To keep data consistancy you should process all not synced entities - both undeleted and deleted.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

storage

private final MemoryLocalStorage storage

Constructor Detail

CategorySyncAdapter

public CategorySyncAdapter(MemoryLocalStorage storage)

Method Detail

upload

public void upload(Uploader<CategoryInfo> uploader)

Description copied from interface: EntitySyncAdapter

Method should process all not synced entities from local storage:

1. convert each entity to Info
2. pass each Info to uploader.upload - it will take care about posting info to server
3. if uploader returned new identifier for item, store it to local entity (that means entity is new and was created on server with new identifier)
4. mark uploaded entity as synced (to not sync it again until it will be changed)
5. store updated entity to local db

To keep data consistancy you should process all not synced entities - both undeleted and deleted. Event if an entity was created and immediatelly deleted in local shorage it is highly recommended to upload it to the server in "deleted" state, receive from server unique identifier for entity and store it locally for future reference. Especially it is important for entities which are linked to other entities (e.g. for commodities, categories, products, taxes).

Specified by:

upload in interface EntitySyncAdapter<CategoryInfo>

See Also:

Uploader

doUpload

private void doUpload(Uploader<CategoryInfo> uploader,
                      SyncCategory cat)

createOrUpdateEntityFromInfo

public void createOrUpdateEntityFromInfo(CategoryInfo info)

Description copied from interface: EntitySyncAdapter

Method should update corresponding entity from info (entity could be located by identifier from info) or create entity if client has no entity with such identifier.

Specified by:

createOrUpdateEntityFromInfo in interface EntitySyncAdapter<CategoryInfo>