Peter Raupp (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=630c5e1...
) *commented* on HHH-15469 (
https://hibernate.atlassian.net/browse/HHH-15469?atlOrigin=eyJpIjoiODY1OT...
)
Re: Missing EntityNotFoundException while using @ManyToOne / @OneToMany and EntityManager
interface (
https://hibernate.atlassian.net/browse/HHH-15469?atlOrigin=eyJpIjoiODY1OT...
)
@Christian Beikov
According to the semantics of JPA, calling persist with a REMOVED entity
will result in the entity becoming managed again.
I'm not questioning that approach at all. The only issue with this JIRA ticket is why
an exception is thrown in one case and not in the other?
When this occurs, I want to be notified about it, whether I'm using a Hibernate
session or the EntityManager.
It is disastrous that in one case an exception is thrown and in the other case not, even
though it is the same semantics.
This is simply a bad quality of the software. It is your decision to reopen the bug and
thus improve the quality of the software.
(
https://hibernate.atlassian.net/browse/HHH-15469#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-15469#add-comment?atlOrigin=ey...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100233- sha1:7fb7fe8 )