-
Notifications
You must be signed in to change notification settings - Fork 40.9k
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
Incorrect target type with wildcard List #18767
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Oct 28, 2019
snicoll
changed the title
Heap pollution with ConstructorBinding
Incorrect target type with wildcard List
Oct 28, 2019
Thanks for the sample. I've edited your title to clarify the issue is not related to constructor binding (I can reproduce with regular JavaBean accessors as well). |
snicoll
added
type: bug
A general bug
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Oct 28, 2019
snicoll
added a commit
to snicoll/spring-boot
that referenced
this issue
Oct 28, 2019
This is a bug in Spring Framework's |
mbhave
added
the
status: blocked
An issue that's blocked on an external project change
label
Dec 5, 2019
mbhave
removed
the
status: blocked
An issue that's blocked on an external project change
label
Dec 16, 2019
This was referenced Jan 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When constructor for
ConfigurationProperties
bean has wildcard parameters, Boot doesn't apply converters, but instead keeps String as-is.For example, if parameter is
Map<String, ? extends List<? extends InetAddress>>
(this is how Kotlin translatesList<String, Map<InetAddress>>
into Java bytecode), Boot will pass into constructor a map of lists of strings, while it should have converted those strings intoInetAddress
es.Reproducer:
The text was updated successfully, but these errors were encountered: