> The avoidance of reflective constructor invocation via byte code
generation should be rather simple using ByteBuddy.
Turns out that the ByteBuddy byte code provider already has an
instantiation optimizer doing exactly that [1]. Unfortunately, though, from
what I can say it's never used due to a
I like it, but I think that's two separate concerns:
* using byte code generation to improve performance of entity instantiations
* avoiding the need for entities to have a parameterless constructor,
emphasising the mandatory properties of an entity (by requiring them as
constructor parameters) an
For anyone interested, Josh Long tell more about why they took this
approach where they inject the default constructor:
https://twitter.com/starbuxman/status/960049941916696578
Rafael Winterhaler shows that this can be easily done with Byte Buddy which
we already used before:
https://twitter.com
Hi,
I realized that we could allow users to define entities without a default
constructor.
For Kotlin, which supportsdefault values, this could be beneficial.
There is some info about how we could do that in this using Objenesis in
the following Spring issue:
https://jira.spring.io/plugins/serv
