There's discussion on the mailing lists to let the bean inspection APIs return proper BeanInfo instances for records, too. I.e. .name() would still constitute a "name" property with a ready method of name(). That should make existing libraries work with records OOTB.
Java-brewed engineer with a taste for Kotlin (Compose), a tolerance for TypeScript (React), and a soft spot for Dart(Flutter);
Co-founder of jPrime, jProfessional, DataStackConf and java.beer events
That will be GREAT if it happens, because to patch ALL libraries is a disaster especially with the Java EE to Jakarta EE and JSTL impl or JSF being part of the web container in some cases.. it becomes a huge mess.
I still like get more btw... it's better to be consistent even not great, then inconsistent.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's discussion on the mailing lists to let the bean inspection APIs return proper BeanInfo instances for records, too. I.e. .name() would still constitute a "name" property with a ready method of name(). That should make existing libraries work with records OOTB.
That will be GREAT if it happens, because to patch ALL libraries is a disaster especially with the Java EE to Jakarta EE and JSTL impl or JSF being part of the web container in some cases.. it becomes a huge mess.
I still like get more btw... it's better to be consistent even not great, then inconsistent.