On 2010-10-04 13.52, Niclas Hedhman wrote:
I am working on the Cache Extension system for EntityStores. It would be really cool to be able to specify caching options in the Usecase of UnitOfWork (as metaInfo).Right now the EntityStoreSPI looks like; public interface EntityStoreSPI { EntityState newEntityState( EntityStoreUnitOfWork unitOfWork, EntityReference identity, EntityDescriptor entityDescriptor ); EntityState getEntityState( EntityStoreUnitOfWork unitOfWork, EntityReference identity ); StateCommitter applyChanges( Iterable<EntityState> state, String version, long lastModified ); } The applyChanges() doesn't pass the UnitOfWork in the call, like the other two methods, and without it, I can't get hold of the UnitOfWork and the Usecase for this feature. I suggest that the applyChanges() are changed to pass the EntityStoreUnitOfWork, which I think is needed for this feature and looks like it should have been there in the first place.
Sounds good to me, +1. You have to change the default impl of ESUOW to remember the usecase though, so that applyChanges can use it.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
