Thanks for the feedback.
Yes HibernateMassIndexed (not Impl suffix) would be a better name.
I am thinking that we could use something like what I have done in
bean validation to have Hibernate specific MassIndexer properties type-
safely exposed as a subinterface of the public MassIndexer.
Maybe
Hi Emmanuel,
I guess some classes would result similar in an Infinispan based mass
indexer, bit this is coupled to which are the efficient strategies to
get a continuous flow of Documents.
It mostly depends on how you're going to store structured entities in
Infinispan? The whole graph needed by a
Hey Sanne,
MassIndexerImpl is 100% dependent of Hibernate Core (you pass a
SessionFactory).
How realistic and doable is it to abstract that a bit. For example,
would an Infinispan based mass indexer make sense? If yes, what's
reusable in your impl (I mean aside from the MassIndexer interface)
