|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
If we plan on using the current RI behavior, I'm for renaming the methods getConstrainedNonGetterMethod() and possibly remove hasConstrainedExecutable that is becoming quite useless in that context.
I thought about ExecutableType which is appealing but the exception cases (in particular constructors are problematic).
Otherwise, I think my preference would go for something like what Gunnar proposes.
getConstrainedMethods(MethodType... type) where MethodType is GETTER, NON_GETTER. It's more verbose but future proof compared to the boolean. But I could be convinced of the boolean version.
Same for hasConstrainedExecutable which would likely take an ExecutableType though but I could be convinced that this one is not useful enough and should be removed for now.