Supported nested conversions for AggregateReference.
Restructured reading conversion process into:
- converting technology base types (JDBC Arrays).
- standard and custom conversions.
- module specific conversions (AggregateReference).
Closes https://github.com/spring-projects/spring-data-relational/issues/1828
I left a few comments. I assumed this PR would had addressed the issue of late converter registration so that we can remove
AggregateReferenceConvertersby consideringAggregateReferenceinwriteValue(andreadValue). We should revisit those converters for having a cleaner approach and to not distribute conversion ofAggregateReferenceto components outside ofMappingRelationalConverter/MappingJdbcConverter.
I was able to simply remove AggregateReferenceConverters. They weren't used anymore.
Oops.
Ready for another round of review.
That's merged and polished now. For the time being, I suggest keeping that change for 4.0 only and if it proves to not create downstream issues, we can consider it for backporting.