{"push_id":1519766178,"size":1,"distinct_size":1,"ref":"refs/heads/1.10.x","head":"9c6a6a750bdbccce999d25e67c4934d9b3bb8b36","before":"6bd2d9eabe3d798e6f462a284fa44d83790f3504","commits":[{"sha":"9c6a6a750bdbccce999d25e67c4934d9b3bb8b36","author":{"name":"Oliver Gierke","email":"38ee5bac45ff50652649d3de34db6078888e1972@pivotal.io"},"message":"DATAJPA-1005 - Improved lookup of EntityManagerFactory bean definitions for constructor injectability.\n\nOur bean definition check for EntityManagerFactory instances previously expected the type prediction to return exactly EntityManagerFactory. That should theoretically always be the case as the component inspecting the beans is a BeanFactoryPostProcessor, i.e. running before any of the beans should have been instantiated.\n\nIf however an EntityManagerFactoryBean is already in creation and the EntityManagerFactory backing it is already available, the factory bean will return the concrete factory's type (see AbstractEntityManagerFactoryBean.getObjectType()) so that we have to accept subtypes of EntityManagerFactory in our selection process.\n\nRelated ticket: DATAJPA-1045.","distinct":true,"url":"https://api.github.com/repos/spring-projects/spring-data-jpa/commits/9c6a6a750bdbccce999d25e67c4934d9b3bb8b36"}]}
{"actor":{"display_login":"olivergierke"}}