Switch constructor injection of the repository interface for repository factory beans [DATACMNS-891]

[spring-projects-issues]

Oliver Drotbohm opened DATACMNS-891 and commented

The resolution of the actual bean type produced by repository factories is currently implemented by a predicting BeanPostProcessor. That causes issues for BeanFactoryPostProcessor instances that want to tweak the application context setup by making type based decisions. An instance of that is the automatic replacement of beans with mock instances in Spring Boot 1.4.

If we switched to constructor injection of the repository interface into the factory, the repository interface would even be handed to it for type predicting purposes on the actual factory. We could get rid off the special BeanPostProcessor and make the Boot use case work

---

Issue Links:

• DATACASS-369 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATACOUCH-262 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATAES-315 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATAGRAPH-939 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATAKV-153 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATALDAP-9 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATAMONGO-1566 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATAREDIS-583 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATASOLR-344 Adapt API in RepositoryFactoryBeanSupport implementation
  ("is depended on by")
• DATACMNS-892 Expose repository interface via attribute on bean definition for repository factory beans