boxed booleans and getters

[robertlemmen]

boxed boolean properties where the accessor is of the "isProperty()" format, this can be worked around by adding a ugly "getProperty()" accessor.

I guess IntrospectionUtils::findReadMethodHandle() should include boxed booleans when switching the accessor pattern to look for...

[sai-pullabhotla]

@robertlemmen -

Thanks for the PR.

This was intentional as boxed Booleans have a third state of NULL, in addition to the true/false. IDEs, tools like Lombok, also generate a getXXX method for boxed booleans.

If we need to start supporting isXXX for boxed boolean, it should be fully backward compatible. In other words, we first check for getXXX method, in the event that it is not present, then fall back to isXXX. This ensures we are backward compatible. Let me know your thoughts.

[Mistic92]

For me it's important to have 3 states in Boolean. Like yes/no/nodecision. So as @sai-pullabhotla sad, it should be backward compatible and not crash others code logic