This week's book giveaway is in the Other Languages forum.
We're giving away four copies of Functional Reactive Programming and have Stephen Blackheath and Anthony Jones on-line!
See this thread for details.
Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Bidirectional @OneToOne with JoinTable

 
Subhendu Mahanta
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have 2 entities :Customer & Address.

With @OneToOne and @JoinTable Customer.java looks like this:



Now Address.java



When I try to persist a customer I get the following stack-trace:



I have tried this change in Address entity:



with no effect. Surely this could be done without using JoinTable.But I want to do it this way for academic interest.Is it possibe?
 
Ran Pleasant
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I assume that this design is part of a learning experience. However, if this is a production design then you should ask yourself, Does an address really need to point back to its owner?
 
Subhendu Mahanta
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Ron.
You are correct that this is part of a learning experience.There is no need for address to point back to customer.Let's say there are 2 entities A & B which have a bi-directional association. In that case I think shared primary key will be the preferred technique.
 
Subhendu Mahanta
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I wanted to mean "Thanks Ran".Sorry for the typo.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic