On Wed, Jun 18, 2008 at 9:17 PM, Michael Hunger <[EMAIL PROTECTED]> wrote: > I don't think it is reasonable for an entitystore to access the store of an > entity state. As stated previously by
Of course, I guess I didn't understand what you were trying to say before. > Rickard there is only one EntityStore per Module and so per EntityComposite. > What the RMI store tries to do is to > distribute/delegate the storage operation of the entities to the different > entity stores of the entity composites. (But > only for prepare, the other operations are performed with the default entity > store thats injected (in this case a > MemoryStore). Yes, from my understanding is that the RmiEntityStore is "just another store" on the client, operating with exactly the same semantics on the client side, and it interacts with a server object that acts as a UoW client on the server side. I am still a bit dizzy on the classloading implications involved. I guess the assumption is that the classes are available/visible to the EntityStore, but we will need to change that for it to work correctly in an OSGi setup. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
