EntityRepository is optional, so default hierarchy might be misleading here ;) Similar as EntityRepository or CriteriaSupport, EntityManagerDelegate was rather something to put on top of a repo, that's primarily why I didn't extend EntityRepository from it. Also I had the impression that having save, persist and merge would be confusing - seems like that assumption was not correct :)
On Sun, Aug 23, 2015 at 7:42 PM, John D. Ament <johndam...@apache.org> wrote: > On Sun, Aug 23, 2015 at 12:39 PM Thomas Andraschko < > andraschko.tho...@gmail.com> wrote: > > > Thats not required. You can just extend/implement EntityManagerDelegate > > > > Thanks for pointing that out. I missed that note in the docs. > > Is there a reason that this isn't the default hierarchy? > > > > > > 2015-08-23 17:37 GMT+02:00 Harald Wellmann <hwellmann...@gmail.com>: > > > > > +1 > > > > > > Regards, > > > Harald > > > > > > > > > > > > Am 22.08.2015 um 03:23 schrieb John D. Ament: > > > > > >> All, > > >> > > >> Based on the findings from Harald, and the general issues being seen > > with > > >> EntityRepository I'd like to propose that we add merge and persist > > methods > > >> to the EntityRepository interface. > > >> > > >> Both methods would delegate down direct to the underlying > > EntityManager's > > >> methods of the same signature and have the exact same behavior. This > > will > > >> give app developers direct access in cases where they want to > explicitly > > >> call one or the other. > > >> > > >> John > > >> > > >> > > > > > >
