I've been following this in the background here and just wanted confirm something Dan said a few days ago:
On 20 Mar 2014 at 15:59, Dan Haywood wrote: > So I still think it'd be worth considering wrapping up a domain service as > a DN StoreManager impl. I imagine that a lot of the boilerplate could be > factored out. Just looking at the datanucleus-json implementation of > StoreManager [1], for example, it doesn't look *too* threatening. I also > noticed that DataNucleus has a FederatedStoreManager, so there could be a > number of companion store managers for managing entities from these > external systems, operating alongside any entities that Isis itself manages > in the regular JDO ObjectStore. Does this support a convenient idea of different store managers for different entities? I had to hack something a while ago when I needed a particular class to be persisted with one datastore and the rest with the default. I ended up implementing a dummy datastore that was given to Isis, and it decided between my special store for persistence related queries affecting entities of my one class and the "normal" datastore for all the others. It worked, but it was a hack. Is there a better / managed method for this with DN? Regards, Kevin
