title: Mixing DAO and service calls
body: <p>Let's say we have some layer above service layer, with web controllers for example. Service layer is in turn above DAO/Repo layer. In the upper layer the service calls are used alongside repo calls. It breaks the layering of the application to some extent, but should we really bother about wrapping repo methods like <code>findAll()</code> into service methods. I don't think so. Are there any drawbacks that might cause a lot of pain because of such design? Transactional issues?</p>