Hi guys, I'd like to use Qi4j for a project but my use case raise some questions.
My entities have to be persisted in home-made formats and custom supports. Plus, I'd like to change the storage implementation at assembly. Let's imagine I'd like to persist Foo entities in XML files, Bar entities as byte[] in a hardware device acceded through native calls and Zoo entities in a remote service. It seems to me that I have the two following options: 1. use Entity composites, persisted in EntityStore using UnitOfWork lifecycle 2. use Transient composites, explicitely persisted by Repositories, more DAOish First option seems to be the Qi4j/DDD way but I cannot see clearly how to implement it. I could split my Domain Layer in three Modules, each one using a dedicated EntityStore. From what I've understood reading the Qi4j code I won't be able to use EntityFinder and the Query API as it is currently "limited" to SPARQL. Second option feels easier to implement but I feel that it's not the right way to do it. What do you think ? Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
