On Thu 2014-03-27 12:40, Hardy Ferentschik wrote:
> the tricky part is that today SearchFactoryIntegrator extends
> SearchFactory, but since SearchFactoryIntegrator needs to say in
> Engine, it can't depend on SearchFactory. What would you think of
> breaking this parent-child relation?
> From a user's perspective they wouldn't be able to narrow down their
> SearchFactory to an SearchFactoryIntegrator, but we could provide an
> unwrap backdoor.
I am not following you. You no longer want a common SearchFactory
interface usable across all event source implementations?