-
Notifications
You must be signed in to change notification settings - Fork 38.2k
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
Document why complex object structure are not supported as paremeters or properties by AOT #32273
Comments
It's not really the same thing. The issue you've referenced is a limitation of a supported construct of the core container. Creating a bean definition with an instance supplier is totally supported but, for obvious reasons, can't be supported by the AOT engine. Providing complex object structure to a
I disagree with that. There's nothing specific with |
With the work going on in #32777 this will generate the following:
Let's rephrase this to have a section in the reference doc that rather explains why this exception is thrown. Conveying that in the exception message is not really practical. |
Affects: 6.1.3
A bean definition that uses non-common value types like this:
will cause a
ValueCodeGeneration
exception.Since this use case is intentionally unsupported (see #32214 (comment)), a helpful error message saying "
ConstructorArgumentValues
do not support code generation for arguments of type (MyBeanRecord)" should be thrown instead, similar to what happens with instance suppliers.Demo: https://github.com/Christopher-Chianelli/issue-reproducer/tree/constructor-argument-value-unsupported/demo
The text was updated successfully, but these errors were encountered: