RE: EntityRepository + EntityManagerDelegate

sitory API in > the same class causes “breakage”? > > > > Would you mind elaborating? > > > > _Marvin > > > > *From:* Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > *Sent:* Wednesday, December 9, 2015 6:03 PM > *Subject:* RE: EntityRepository + EntityManagerDele

RE: EntityRepository + EntityManagerDelegate

Without having the benefit of "test driving" the change, it seems to make a lot of sense to me. Any approach enabling direct access to the (native) JPA API can only be beneficial when it is impossible to imagine all of the different use cases that might emerge for hundreds of developers over

Re: EntityRepository + EntityManagerDelegate

I like the convenience of only needing to extend one interface, and like that it still allows the old flexibility of only extending what you need. John On Wed, Dec 9, 2015 at 4:26 PM Harald Wellmann wrote: > For the benefit of all DS Data users who prefer persist() and

RE: EntityRepository + EntityManagerDelegate

Doesnt it break data design? Why not using the em if it is what you need? One doesnt prevent the other. Le 9 déc. 2015 23:12, "Marvin Toll" a écrit : > Without having the benefit of "test driving" the change, it seems to make > a lot of sense to me. Any approach

RE: EntityRepository + EntityManagerDelegate

causes “breakage”? Would you mind elaborating? _Marvin From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: Wednesday, December 9, 2015 6:03 PM Subject: RE: EntityRepository + EntityManagerDelegate Doesnt it break data design? Why not using the em if it is what you need? One