-
Bug
-
Resolution: Fixed
-
P3
-
11, 12, 13
-
b24
-
b15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8229996 | 11.0.6-oracle | Dmitry Cherepanov | P3 | Resolved | Fixed | b01 |
JDK-8223855 | 11.0.4 | Dmitry Cherepanov | P3 | Resolved | Fixed | b03 |
Described here:
https://mail.openjdk.java.net/pipermail/beans-dev/2019-March/000405.html
The behavior of PropertyDescription.getReadMethod has been changed for boolean properties. Previously (for 8), the "is" getter was used when both "is"/"get" getters provided. However now (since 9), the "get" getter is used in this case.
It violates the JavaBeans API spec, quotation from the spec - This "is<PropertyName>" method may be provided instead of a "get<PropertyName>" method, or it may be provided in addition to a "get<PropertyName>" method. In either case, if the "is<PropertyName>" method is present for a boolean property then we will use the "is<PropertyName>" method to read the property value.
https://mail.openjdk.java.net/pipermail/beans-dev/2019-March/000405.html
The behavior of PropertyDescription.getReadMethod has been changed for boolean properties. Previously (for 8), the "is" getter was used when both "is"/"get" getters provided. However now (since 9), the "get" getter is used in this case.
It violates the JavaBeans API spec, quotation from the spec - This "is<PropertyName>" method may be provided instead of a "get<PropertyName>" method, or it may be provided in addition to a "get<PropertyName>" method. In either case, if the "is<PropertyName>" method is present for a boolean property then we will use the "is<PropertyName>" method to read the property value.
- backported by
-
JDK-8223855 Unexpected behavior of PropertyDescription.getReadMethod for boolean properties
- Resolved
-
JDK-8229996 Unexpected behavior of PropertyDescription.getReadMethod for boolean properties
- Resolved
- relates to
-
JDK-4058433 RFE: tool for creating BeanInfo template
- Resolved