Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce uniform GenericConverter interface within the GenericConversionService implementation [SPR-6139] #10807

Closed
spring-projects-issues opened this issue Sep 21, 2009 · 0 comments
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Keith Donald opened SPR-6139 and commented

Currently the GenericConversionService implementation indexes Converters and ConverterFactories directly under these specific SPI interfaces, and has a nasty if/else block for special-case "generic converters" that require full access to the source/target property binding context (via TypeDescriptor). We should introduce a uniform GenericConversionService all type converters are indexed under in the GenericConversionService, including user-defined Converters, ConverterFactories, and special-case GenericConverters.


Affects: 3.0 M4

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 RC1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant