I think we can exclude synthetic methods there as well as e.g. in case of bridge methods we'll process the actual method anyways. I thus don't believe there is a case where we'd need to replace synthetic methods with their overridden counterpart in ValidationExtension#determineConstrainedMethod(). Any thoughts, Hardy Ferentschik?

Sounds reasonable. I think as well we should just ignore synthetic methods.