This is a really lazy complaint that gets reiterated when this approach is mentioned. There's no elaboration here to provide substance to the argument. When I

This is a really lazy complaint that gets reiterated when this approach is mentioned. There's no elaboration here to provide substance to the argument. When I think stereotypical enterprise java complaints, I think people joking about AbstractFactorySingetonProxyBeanAdapterFacadeConcrete. Not this. Whether you agree with the approach or not, it's fair to say that the author is simply drawing some boundaries around his/her business logic to make it framework agnostic, decoupled, and test-speed friendly.