I second Bertrand on this. The whole point of Sling is that it's a REST framework with a straightforward CRUD support. I feel there's a tendency for people to attempt to shoehorn in paradigms from other application frameworks, because it's familiar to them, and they end up with a layer of complexity that isn't needed.
-----Original Message----- From: Bertrand Delacretaz [mailto:[email protected]] Sent: Tuesday, July 28, 2015 10:28 AM To: users Subject: Re: Best practices for java DTOs to/from Sling On Tue, Jul 28, 2015 at 4:02 PM, Haefele, Michael <[email protected]> wrote: >... If we end up doing a lot more DB-style work (particularly updates), >I think I'll push for some budget to switch to one of the OCM technologies.... Note that the general thinking here is still that OCM is not needed with Sling, in the vast majority of cases - the underlying resource model is sufficiently flexible that OCM looks just like an extra layer that's not really needed. There are some exceptions and YMMV of course. -Bertrand
