Sep 20th, 2011, 03:46 AM
custom repository implementation names pattern
I spent an hour debuging a strange problem. Finally the source of all was the internal mechanism that detects the custom repository implementation names. I have a repository UnitRepository and a custom implementation UnitRepositoryCustom with the clas UnitRepositoryImpl. But in my application I also have another repository PoliticalUnitRepository that wasn't related to UnitRepository. AbstractRepositoryConfigDefinitionParser.detectCus tomImplementation() binds the PoliticalUnitRepositoryImpl to UnitRepository. Is this the intended way? In that case the PoliticalUnitRepositoryImpl must extend the UnitRepositoryImpl. Please update the reference documentation with a warning.