From what I see in the code, it probably makes sense for these checks to occur in the isMutator() method... it's only used in one place, and if you find yourself duplicating the checks in getMutator() that are not included in isMutator() for some reason, then it's possible those additional checks should be pulled into the method. It's an implementation detail, and if pulling this together makes the code simpler, I'm all for it.

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