Over a million developers have joined DZone.

@OneToOne With Shared Primary Key, Revisited

DZone's Guide to

@OneToOne With Shared Primary Key, Revisited

Take another look at @OneToOne with a shared primary key.

· Java Zone
Free Resource

Make it happen: rapid app development on Kubernetes as a managed service.

Long time ago, I wrote a post @OneToOne with shared primary key. Today I would like to return to this problem, with solution based on @MapsId annotation introduced in JPA 2.0

Again we have two entities: Primus and Secundus. Both entities have primary key using Long Java type. They are related 1-1, and Secundus should use the same primary key as Primus.
3 Years after my initial post they will look slightly different ;)

@Table(name = "PRIMUS")
public class Primus {

    public static Primus newInstance() {
        Primus primus = new Primus();
        primus.secundus = new Secundus(primus);
        return primus;

    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    @OneToOne(cascade = CascadeType.ALL, mappedBy = "primus")
    private Secundus secundus;

    Primus() {


Not much changed here, ;). Really important changes were made on the Secundus:

@Table(name = "SECUNDUS")
public class Secundus {

    private Long id;

@JoinColumn(name = "ID")
    private Primus primus;

    Secundus() {

    public Secundus(Primus primus) {
        this.primus = primus;

As you see, the @PrimaryKeyJoinColumn annotation is replaced with two annotations: @MapsId, which defines thatSecundus identifier will be determined by Primus identifier, and @JoinColumn, specifying which column in SECUNDUS table will be used for joining.

Nothing more is needed :) - JPA Provider should automatically ask Primus for its identifier, when persistingSecundus, as long as you take care of correct entities correlation, like in newInstance method of Primus.

Long live JPA 2.0+ ;) :)

Tutorial: WordPress as distributed microservices on Kubernetes.

java ,persistence ,jpa 2.0

Published at DZone with permission of Michal Jastak, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}