>> Why does not JdbmEntityStore know about its content and how would I >> explain it to him? > > You are now on 'slippery slope' territory ;-) > > There is a contract between the UnitOfWork and the EntityStores, where > the EntityStore doesn't know anything about the types to be stored > initially, and throws this exception when they need to be informed. > UoW will when getting such exception call a registerEntityType() to > populate such information. > Since the registerEntityType() method is highly serializable and does > not contain any application level types, it is possible to have > EntityStores remotely that does not have any 'application specific' > configuration or classes.
Sorry, I am totally confused. I am not sure if you are suggesting some way to fix it or you are explaining the impossibility of it being fixed? :-) In general, is this a reasonable approach? If not what is? What confuses the hell out of me is why I need the indexer in the first place; I have the entity store, why on earth would I need the indexer? I mean if query by id it goes straigth to the entity store but if I do findAll it needs RdfQueryService (well I guess it needs EntityFinder which happens to be RdfQueryService). _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
