Agreed... mixing the JPA API ("persist" / "merge") with an abstraction API
("save") is confusing.
Said another way... the goals of an abstraction to provide convenience and
reduce the learning curve is being thwarted by too many choices and an extended
learning curve.
-----Original Message-----
From: Thomas Hug [mailto:[email protected]]
Sent: Monday, August 24, 2015 5:00 PM
To: [email protected]
Subject: Re: [DISCUSS] Add persist and merge methods to EntityRepository
Also I had the impression that having save, persist and merge would be
confusing - seems like that assumption was not correct :)
