EntityStoreSPI.applyChanges() should have the EntityStoreUnitOfWork passed
along.
---------------------------------------------------------------------------------
Key: QI-267
URL: http://issues.ops4j.org/browse/QI-267
Project: Qi4j
Issue Type: Improvement
Components: SPI
Reporter: Niclas Hedhman
Assignee: Rickard Öberg
Fix For: 1.2
NOTE: This change is incompatible at Entity Store SPI level!!!
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
