[
https://issues.jboss.org/browse/ROASTER-13?page=com.atlassian.jira.plugin...
]
Matej Briskar edited comment on ROASTER-13 at 5/14/14 11:25 AM:
----------------------------------------------------------------
However, if the {code}#isMutator(){code} already access the property name to check the
name of the property, wouldn't it be better if it does the job completely and do the
checks that are now done afterwards in the method {code}#getMutator(){code}
was (Author: mbriskar):
However, if the `#isMutator()` already access the property name to check the name of the
property, wouldn't it be better if it does the job completely and do the checks that
are now done afterwards in the method {code}#getMutator(){code}
PropertyImpl is not checking return type/parameter type in
isAccessor() isMutator() methods
-------------------------------------------------------------------------------------------
Key: ROASTER-13
URL:
https://issues.jboss.org/browse/ROASTER-13
Project: Roaster
Issue Type: Bug
Reporter: Matej Briskar
Assignee: Matej Briskar
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)