[hibernate-issues] [JIRA] (HHH-845) .id should not be specific anymore in a EJB3 compliant mode

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Out of Date* At least since Hibernate 6 we only allow the special name `id` as a last resort, so this should not be an issue anymore. Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjczNDFjNGE1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-845?atlOrigin=eyJpIjoiZjczNDFj... ) HHH-845 ( https://hibernate.atlassian.net/browse/HHH-845?atlOrigin=eyJpIjoiZjczNDFj... ).id should not be specific anymore in a EJB3 compliant mode ( https://hibernate.atlassian.net/browse/HHH-845?atlOrigin=eyJpIjoiZjczNDFj... ) Change By: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Resolution: Out of Date Status: Open Closed ( https://hibernate.atlassian.net/browse/HHH-845#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-845#add-comment?atlOrigin=eyJp... ) 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#100210- sha1:cad9577 )