In particular, these tests need to check that Search, in a Spring or CDI environment, is able to instantiate components from the Spring/CDI context, and that Spring/CDI features can be used in those components (@PostConstruct, @Inject, ...).

We already have several tests for that in Search 5, both for Spring and for CDI in a JEE server (WF). Maybe we should just stick to CDI in a Java SE environment for now, as we don't have support for WF yet.

While we're at it, we should make sure that all user-defined components can be instantiated from the Spring/CDI context: in Search 5 that was only available for bridges, but it should now be available for ContainerExtractors, Configurers, ... Maybe that's too many combinations to test, though.